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.
2234b50047b7c9ac78ab02ea29e6263f6251dcb2060e676461a2e6b03ea2ec80
Both payments are on their chains and locked to the same secret hash 17756b02fbf88bc73d11d94cb9e4197a999246b9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2234b50047b7c9ac78ab02ea29e6263f6251dcb2060e676461a2e6b03ea2ec80
- MakerPaymentSpent: 2857438b0e17954dff9aa39bc76bb9fe1f0a9e3476d2bc432aee56c7ffe8bd9f
0e8f1908bf114a2c72b02551d1a35da6ab2ee6f0e86912a8c30dd63570f0e8f8
Both payments are on their chains and locked to the same secret hash 17756b02fbf88bc73d11d94cb9e4197a999246b9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4cc2ce815fadf50706153cb0311af72b13c11129081ccff0ae2f5244e6a75772
- TakerPaymentSent · TakerPaymentReceived: 0e8f1908bf114a2c72b02551d1a35da6ab2ee6f0e86912a8c30dd63570f0e8f8
- TakerPaymentSpent: 78697a4eee6dd6e88295331f2ca1e655d2287b88ee86e273d965ebd703cbd7b7
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.