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.
6257d23ae53142987fd9d0b90c50889b41e5decf0b287635855367bc1073fdfc
Both payments are on their chains and locked to the same secret hash 0d3e5cea713b2341e60b766a5398ace423a1188e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6257d23ae53142987fd9d0b90c50889b41e5decf0b287635855367bc1073fdfc
- MakerPaymentSpent: 618c0b144308e61c245ce036ef8bff78ba8aacfe10d59ab339715ee9522bc83b
b405a4d57182017933c993947259e76c729ca686bba27db12d50a93bf28ef870
Both payments are on their chains and locked to the same secret hash 0d3e5cea713b2341e60b766a5398ace423a1188e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7b1ee438f782bd1f49ebd83c87e7a0251defe2f27bda299a48cacd68b1468f29
- TakerPaymentSent · TakerPaymentReceived: b405a4d57182017933c993947259e76c729ca686bba27db12d50a93bf28ef870
- TakerPaymentSpent: 63bf0b27cd5d9b108248c52af1ad983c6eae64214c501d07a6b8feabf804b8b6
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.