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.
acab0decc6aac42f9937fdd988515da4074b5510434f3f837a1d780fe0ace9e4
Both payments are on their chains and locked to the same secret hash 3640b493326a7a13d0eef295fde9fe56f144074f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: acab0decc6aac42f9937fdd988515da4074b5510434f3f837a1d780fe0ace9e4
- MakerPaymentSpent: a4a096f0283581a2742931ef2e0383cdd3d298dbabe706049fe50945d3d3cb4e
7548159cfc4fb744db09d0136fe702980dd7819014e9a6b425b7837509a15142
Both payments are on their chains and locked to the same secret hash 3640b493326a7a13d0eef295fde9fe56f144074f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5397b5a7f0beca74a42379b41b05e10cd4ce9ed9547524fe030a311c6a41ec01
- TakerPaymentSent · TakerPaymentReceived: 7548159cfc4fb744db09d0136fe702980dd7819014e9a6b425b7837509a15142
- TakerPaymentSpent: c853aef96e196af060544c2c2e9c379eb473c75cf16ce16b45bb9fbdfdb17022
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.