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.
e2bf22b00ba6446cd5a905ac46078cec7e498383e12261494c357d949b8aa928
Both payments are on their chains and locked to the same secret hash da8b8f0285e277ad3e89fcd1ed3d1f82a8591685, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e2bf22b00ba6446cd5a905ac46078cec7e498383e12261494c357d949b8aa928
- MakerPaymentSpent: 76a048935b6a35342781e2e5edd59206da849d72687578e30d0ea71ce2e3b6a7
661387cf739763f0ca27d5fc39854618e9902e845db83d9dee53cde9fb09aac2
Both payments are on their chains and locked to the same secret hash da8b8f0285e277ad3e89fcd1ed3d1f82a8591685, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7425d94c37eb7ffc770ce6473222614e58c014425f04a5b00409bbe7600c7a3c
- TakerPaymentReceived · TakerPaymentSent: 661387cf739763f0ca27d5fc39854618e9902e845db83d9dee53cde9fb09aac2
- TakerPaymentSpent: ff97208002b8980115712bb487f2f05afe79253ad9de439aa3208b21414fe2dc
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.