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.
1e51f16b069b741f2edf476ce9e214dd1164c89bcce8ab6b08678e17cd7eca59
Both payments are on their chains and locked to the same secret hash af5555539aaa0ec0a0c03ba3973ede849c8f283c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 1e51f16b069b741f2edf476ce9e214dd1164c89bcce8ab6b08678e17cd7eca59
600043c0ded195c1df385fc855e16c7b1c7aa43424d25c8ff2b75ae745108b8f
Both payments are on their chains and locked to the same secret hash af5555539aaa0ec0a0c03ba3973ede849c8f283c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 9e4624781d1de30133cb8bdf61444df71eeec140eab2ec041bb7eb07d979ae44
- TakerPaymentReceived: 600043c0ded195c1df385fc855e16c7b1c7aa43424d25c8ff2b75ae745108b8f
- TakerPaymentSpent: b83e94633e0277a84783f3d61536bf1f061c36836325f68143d115710bcdb2e6
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 defistats-gleec.