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.
1251ea2b811a02c4cd45a041050501ed34b9baec2b01e94804b2ce06c4f969da
Both payments are on their chains and locked to the same secret hash 785ddf362c755dff0f3180e539000d317be6e0a8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 1251ea2b811a02c4cd45a041050501ed34b9baec2b01e94804b2ce06c4f969da
- MakerPaymentSpent: a1ef6310c87c056d8fc0245b537f7c5f0bd5c5910190ebfa8d7ab419fc4e6f56
69eefc212beed5cf95a41485a6707b48ae1e600e07c28f8cad1b0c8a8fc66be7
Both payments are on their chains and locked to the same secret hash 785ddf362c755dff0f3180e539000d317be6e0a8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0e21564ca55efa45cca19c268d3d811f1d99204c3adf9c037637e7baebb9acd4
- TakerPaymentSent · TakerPaymentReceived: 69eefc212beed5cf95a41485a6707b48ae1e600e07c28f8cad1b0c8a8fc66be7
- TakerPaymentSpent: d177285fa24b99e77d1b6b5724d985ebf1803e49357e781a8837a685b8ae4a34
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.