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.
51ab8c127e45ee0bff9a130073956cc0c31d06a66c8bc82881acadf4795ca04f
Both payments are on their chains and locked to the same secret hash 07b8eb52476a15340a2e4478dc321ebce4fb77c8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 51ab8c127e45ee0bff9a130073956cc0c31d06a66c8bc82881acadf4795ca04f
- MakerPaymentSpent: fc80b358c66d4c7c67aaa967889d15a0d5922e8b39ddcc7d57337a618ec4155b
5f6d7864db6320fbc205a6bf34632ada5c1bc94374c73d98bd68ddfbc9052d12
Both payments are on their chains and locked to the same secret hash 07b8eb52476a15340a2e4478dc321ebce4fb77c8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 77d52821f7f32cc520c70007f87374ab99acedc56bcafba5a1038a7dc439d997
- TakerPaymentSent · TakerPaymentReceived: 5f6d7864db6320fbc205a6bf34632ada5c1bc94374c73d98bd68ddfbc9052d12
- TakerPaymentSpent: 6c76f74a61aa98ba0f2286db768b90def8f08d253c73232b3be006f343929ac8
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.