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.
dcc59606f2aad6ba034ada2252a0917ad02c66a518d606e5737229840d9af95f
Both payments are on their chains and locked to the same secret hash 56e6cf00926a1b86e830bdd6bb5e499e48e4e9f9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dcc59606f2aad6ba034ada2252a0917ad02c66a518d606e5737229840d9af95f
- MakerPaymentSpent: fd73aa235d4a4a4b18cd0ba80b33ba1ce2487208dbcf108b33bf3e9929dc6d72
0e740b4718fca7eaa1c43f6e5df5dbcd8ce201fc876bc7f5dcd80f31ad8f5b44
Both payments are on their chains and locked to the same secret hash 56e6cf00926a1b86e830bdd6bb5e499e48e4e9f9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 590ad89a5689fe93f256f9b552b073a88985f6fdb30b7f43cb1c2aaba3133d25
- TakerPaymentSent · TakerPaymentReceived: 0e740b4718fca7eaa1c43f6e5df5dbcd8ce201fc876bc7f5dcd80f31ad8f5b44
- TakerPaymentSpent: 2aa72f72c30c7592897a273bceba878dd89bf9cada81e95f04e893e198b2f7b4
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.