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.
9aec45c0715b574170c26368aab173ae2d777150ee2fc1f8d4f5460b99168faa
Both payments are on their chains and locked to the same secret hash ed2bead7b80981edd75887c3b8ccfb3a9e2d3abe, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9aec45c0715b574170c26368aab173ae2d777150ee2fc1f8d4f5460b99168faa
- MakerPaymentSpent: 700ac6def68b225df4cfa61d0381e5c03cf6c97bfd0be47cc70b6d91aece0273
3601b08e15fa0370dfbb9677b0753cafa79909bd0af6f8b1b37afa151b4d8e8c
Both payments are on their chains and locked to the same secret hash ed2bead7b80981edd75887c3b8ccfb3a9e2d3abe, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: b2404eac8a253d468cba5f2c5d3a42490509378a6fa274c9e71ed4dd60e3ef27
- TakerPaymentReceived · TakerPaymentSent: 3601b08e15fa0370dfbb9677b0753cafa79909bd0af6f8b1b37afa151b4d8e8c
- TakerPaymentSpent: bd63c8fb20a3d84573cbbd59f11b7548f0152484919172f8182d498745258f85
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.