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.
0cd1796c6b5a0beb8dcb2d8b0e45dc09daa8080bdca8828a4dfcb9bd2089c0f7
Both payments are on their chains and locked to the same secret hash bc9ec8f46720ed34564a602a68c17f6c18e47ad3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0cd1796c6b5a0beb8dcb2d8b0e45dc09daa8080bdca8828a4dfcb9bd2089c0f7
- MakerPaymentSpent: e950c9b86dd6cf7e8b34254207276bb16c98b6253c494e962f248e4dffeb6755
cf08966e1876cb10be0015a96df2d057f574cb164168b6589240e267e704bb7b
Both payments are on their chains and locked to the same secret hash bc9ec8f46720ed34564a602a68c17f6c18e47ad3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 88986734f65bf0582f9318d5cab4d1f9750e28c5d4ab6e204f2111401f22251b
- TakerPaymentSent · TakerPaymentReceived: cf08966e1876cb10be0015a96df2d057f574cb164168b6589240e267e704bb7b
- TakerPaymentSpent: a1334d92b6a159037947f578fcd719e01f0d1e30b8fbbb16229bdbd499fdb281
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.