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.
f4aeba42d6408ae39688e5509c98456208fd5d83c67dda5eac8cf49dfd4de81e
Both payments are on their chains and locked to the same secret hash 69d3de54b91f4af90abd30378a32e06e9b0d8ec9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f4aeba42d6408ae39688e5509c98456208fd5d83c67dda5eac8cf49dfd4de81e
- MakerPaymentSpent: 9f85e4130a6d9585470b6bd50ab09a15869d1f63fc25913747a3cf2560c2abb3
d3dca9c5255a0b34289a1fa4afe1557df6d4b9a33b5c06d97baf74355f25f774
Both payments are on their chains and locked to the same secret hash 69d3de54b91f4af90abd30378a32e06e9b0d8ec9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8325614571ecfd900a631b6690f084a5127d2044ca12eec43552bc7a7f58cc8b
- TakerPaymentSent · TakerPaymentReceived: d3dca9c5255a0b34289a1fa4afe1557df6d4b9a33b5c06d97baf74355f25f774
- TakerPaymentSpent: 2ef43e1ef4ddedc56f973b24c5fa13106c80abf65dbf0c70ba75830f06164a0b
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.