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.
0937d213430bde1ef34f3fe3cb3afbd5646e84188c4fc50b0664237a1fc0e40c
Both payments are on their chains and locked to the same secret hash ccde3b2012f4415c71ea07d6e0ae9172858b8077, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0937d213430bde1ef34f3fe3cb3afbd5646e84188c4fc50b0664237a1fc0e40c
- MakerPaymentSpent: 6d3dc7f2d9b16c5c11063bed79636db5e0416e96f034fe0c6316a493b5848eb2
d83ef599915b18b341d4eb50556352c93d7b79dae5c0e7bdf808bf38153bd7a1
Both payments are on their chains and locked to the same secret hash ccde3b2012f4415c71ea07d6e0ae9172858b8077, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6e0380c42888f7923138fb638ea1b83f0288bf29c3aa22c5b7d5c075c0a13d1f
- TakerPaymentSent · TakerPaymentReceived: d83ef599915b18b341d4eb50556352c93d7b79dae5c0e7bdf808bf38153bd7a1
- TakerPaymentSpent: 65e73e98370c54ae541b03f0c3dbde2083e92063f416303375ae4e6ddfea1535
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.