An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
6c53547be442a3892484353364a547fa935b953ff43926ebe3fe932f9d82e17d
Both payments are on their chains and locked to the same secret hash 5ccbbe8feb82a0dcc2fec7d6cf4cebdb8dd8becd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6c53547be442a3892484353364a547fa935b953ff43926ebe3fe932f9d82e17d
- MakerPaymentSpent: f2800f3554b3c681deeea23542aba2e140702a4209805733a27997c6269dbf3f
0562161b928e59e6128bd595bd267c2b7bca71ddd16b81a4762b1b9b896271ca
Both payments are on their chains and locked to the same secret hash 5ccbbe8feb82a0dcc2fec7d6cf4cebdb8dd8becd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0e98e1cc3017909d4079ea62ad9c0cb731a452b08ad7e742cbfcba6b4e9b0af6
- TakerPaymentSent · TakerPaymentReceived: 0562161b928e59e6128bd595bd267c2b7bca71ddd16b81a4762b1b9b896271ca
- TakerPaymentSpent: 3bef96435618e733a8b5ae372dd403eb9580ae64e72311f139fc54ddcf6f0522
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.