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.
62ebe48c6496a2c1e452fbec68db3471067aef1dbd7d53553bf204a9042fa0c1
Both payments are on their chains and locked to the same secret hash 7126b949df6b20cad8129d540ad83e9a291e6966, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 62ebe48c6496a2c1e452fbec68db3471067aef1dbd7d53553bf204a9042fa0c1
- MakerPaymentSpent: 0700b37331d48134f04595e9eec746206e06ff3b294104b77ab3a2fcdf0b8e01
8709319abcb5502479be6ba329eaede60b709a21558756523e152eec5e5aded0
Both payments are on their chains and locked to the same secret hash 7126b949df6b20cad8129d540ad83e9a291e6966, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6a9c471767c7c1fd39bb613d7346a5c4dc28f0a829f7d97e4501831c0279b9a0
- TakerPaymentSent · TakerPaymentReceived: 8709319abcb5502479be6ba329eaede60b709a21558756523e152eec5e5aded0
- TakerPaymentSpent: 6ea249de854d1d5723fe9c8ca62d3bf6016443175f2ad303684070646eca6e88
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.