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.
31986ae721cc705bcdff1f74704ac15782a4db26df88ca640bbd54b11389b016
Both payments are on their chains and locked to the same secret hash f1958c6dd9e3d41e9a70957922e9c265ec63cb63, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 31986ae721cc705bcdff1f74704ac15782a4db26df88ca640bbd54b11389b016
- MakerPaymentSpent: 9f07aed66edffc426209f9c87b31d0fb93060e92078aac43b44de8d0e0fbe58e
4673bd35557bdedad14b7d518260eeca487c4266b729e4d5163f46c9eae9d55a
Both payments are on their chains and locked to the same secret hash f1958c6dd9e3d41e9a70957922e9c265ec63cb63, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5a05892ce0c65e43ca6aec3dac13e5d785a899de9d0c12aecf9036dcb6d1be38
- TakerPaymentSent · TakerPaymentReceived: 4673bd35557bdedad14b7d518260eeca487c4266b729e4d5163f46c9eae9d55a
- TakerPaymentSpent: 376732da37e46f66cb90d8f7f944c4fbd012449866caeeed6ac13894194254ee
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.