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.
f7b0b1bcd4dbfb00736c75632f594e199459a2ab0dcd9fa8650e0608e69689f3
Both payments are on their chains and locked to the same secret hash e4fa8423d2a3a10693b3d333f38d70e0f80a30ce, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f7b0b1bcd4dbfb00736c75632f594e199459a2ab0dcd9fa8650e0608e69689f3
- MakerPaymentSpent: f2aa687fcd9fea467c39c82930e242160a8bad662d34c686e75a21795457d715
eaccc630814b7a29bb657cd3266938a5073e7fe663b63c17344c371b090e9242
Both payments are on their chains and locked to the same secret hash e4fa8423d2a3a10693b3d333f38d70e0f80a30ce, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6a85cf813d9b6f6690af76d91540e1a1dd65b8622e86bab97c53b63ab8f3a5e6
- TakerPaymentSent · TakerPaymentReceived: eaccc630814b7a29bb657cd3266938a5073e7fe663b63c17344c371b090e9242
- TakerPaymentSpent: cafb342b6fdd74eedcb473f301800ee86e66961998abd9436e2ced998e846ac9
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.