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.
e2d1fe5308b3109a6fda0f68dc419d3bf117a6e99b31cf399d69b4ef5ca322d6
Both payments are on their chains and locked to the same secret hash d1ce5a72d0a8469c02ac2eac1e440bb7900f212e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: e2d1fe5308b3109a6fda0f68dc419d3bf117a6e99b31cf399d69b4ef5ca322d6
- MakerPaymentSpent: 2bd00735512ac678e7a9b1e298b35b72bb6e5f848d7cc1569abf1617c9a3e458
2634dd2279a1f89121c2d3c3a8518d155dcd3184edf3f87814322199789c8479
Both payments are on their chains and locked to the same secret hash d1ce5a72d0a8469c02ac2eac1e440bb7900f212e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ad81817ab339cbaf31be202ef027508b900da0e5aa4f647b1e1a6e71e283d80a
- TakerPaymentSent · TakerPaymentReceived: 2634dd2279a1f89121c2d3c3a8518d155dcd3184edf3f87814322199789c8479
- TakerPaymentSpent: 1ac7f1f03c95cb65c9064d06c49780d0ced756b1872a83121399b3ae6a2694ff
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.