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.
c9b92e0c31146fc0a0e16e8f44ffdcd23ff18ebdb0e8cb8cbdcafec13439a40e
Both payments are on their chains and locked to the same secret hash e6cdb0a2badd615d70389990682f91f7fed7ad24, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c9b92e0c31146fc0a0e16e8f44ffdcd23ff18ebdb0e8cb8cbdcafec13439a40e
- MakerPaymentSpent: 72f76519ce25212f65183bb11e56d6e2d2866da15f3efa99eadc9df5bdcbeeb4
bf198b167bc4b081bf5f04a9e19f63850ea1d87bd2fcd50feef0e0556949f6dc
Both payments are on their chains and locked to the same secret hash e6cdb0a2badd615d70389990682f91f7fed7ad24, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dd7ee42aa4c9b30a05f6ef155ead4b8df130e268bab2a579343e3da9f61af671
- TakerPaymentSent · TakerPaymentReceived: bf198b167bc4b081bf5f04a9e19f63850ea1d87bd2fcd50feef0e0556949f6dc
- TakerPaymentSpent: 74a138c747f4d2369e5ea45fd4729ec9e21362870bd262d15983b71043d0b43c
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.