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.
e647a46005814a3412d2774ce5fd885666d7aec76fd5571e4f70ce8ba1d6e9f8
Both payments are on their chains and locked to the same secret hash d9615477a438bff64967053571638b0008172650, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: e647a46005814a3412d2774ce5fd885666d7aec76fd5571e4f70ce8ba1d6e9f8
3c01d0c1e300f035da202925faca54a738f4fc85d30e294fb2c20b6e5fe146f3
Both payments are on their chains and locked to the same secret hash d9615477a438bff64967053571638b0008172650, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 954cd5d37a4ac579dd980ed519b309d34a384e92eef93961528dbaeb04e18e20
- TakerPaymentReceived: 3c01d0c1e300f035da202925faca54a738f4fc85d30e294fb2c20b6e5fe146f3
- TakerPaymentSpent: 03824b4ae62823be89ece016e55abca54bdc7f763b9e676f5cc6affa8ddb4484
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.