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.
b42d8c5ff504c856196d26eb0339b6dae80d85c62ea0bb18e0b541cb78674298
Both payments are on their chains and locked to the same secret hash c5c782b4267587369abf247a65a7b95ffffd606b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b42d8c5ff504c856196d26eb0339b6dae80d85c62ea0bb18e0b541cb78674298
- MakerPaymentSpent: e3c73464b48aadfda94925f18f0eedb58fd6d3f3f39f063d3bfac5acf8395bad
7d2b38fe2c5222a226f99b6d2e381da5eda24239aa8e7871d4b4e0339c3b56c1
Both payments are on their chains and locked to the same secret hash c5c782b4267587369abf247a65a7b95ffffd606b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9f9b973c651c80914e864e76d3d39b090528cfa7d272a5dcaef2fd6a70f7c6f0
- TakerPaymentSent · TakerPaymentReceived: 7d2b38fe2c5222a226f99b6d2e381da5eda24239aa8e7871d4b4e0339c3b56c1
- TakerPaymentSpent: e10b1b41ca446148d561bc0ebd05988deda3805a5c28464b6722643ca286ff84
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.