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.
f6156d9a2fdc0745aa9920b0929fdcd6ca72672d9bc8d0ae5752b757e127bf40
Both payments are on their chains and locked to the same secret hash 983b9b3e855a601f88f6f0bf374390ca56396141, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f6156d9a2fdc0745aa9920b0929fdcd6ca72672d9bc8d0ae5752b757e127bf40
- MakerPaymentSpent: a6a61102bd7077cbee1682f3fe23c0709a30bb8492e1dd7122f6933e70cba60e
449b4aa98e62786a46b2a7c187a634b69f64e952060fa1e2c38edcbad14fd6ab
Both payments are on their chains and locked to the same secret hash 983b9b3e855a601f88f6f0bf374390ca56396141, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8b72d59bb0d0048981893f70dda54d8b04c7dd4923871db32ac0e263052c2fa3
- TakerPaymentSent · TakerPaymentReceived: 449b4aa98e62786a46b2a7c187a634b69f64e952060fa1e2c38edcbad14fd6ab
- TakerPaymentSpent: 97ed49788f0e8a95443bf289187d5992edd67664dd8aaad83fad43f5fec7f232
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.