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.
0e703eb7c70d34239799404381e9a87aa1dffb3475e014f2dbe9d5ca1653a8ff
Both payments are on their chains and locked to the same secret hash b3e7c64b7cb1b02cad17f23b1c92d3f893b9baee, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0e703eb7c70d34239799404381e9a87aa1dffb3475e014f2dbe9d5ca1653a8ff
- MakerPaymentSpent: 789c3761cd31acdbdb30cf5ed1eec50460d14503afccaa84d1590245c4d1802b
1665ea67362ea02a94d41a45383d4726921a71b0ad8a1e81e07544e94848e4d8
Both payments are on their chains and locked to the same secret hash b3e7c64b7cb1b02cad17f23b1c92d3f893b9baee, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f71cfbff3654a5bf6eb9b7418000dbe45238b745519f34a5393762a06c901b69
- TakerPaymentSent · TakerPaymentReceived: 1665ea67362ea02a94d41a45383d4726921a71b0ad8a1e81e07544e94848e4d8
- TakerPaymentSpent: 531111436d20bce312e3d93edc7a8bcac57e2b35dc55f8d4ffe6e24deeb13f26
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.