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.
9a7d2e0c015e6ffc4b6422f45b55c6d3b8e68e7ad1599916d13160b6c914cf9f
Both payments are on their chains and locked to the same secret hash 955d72993a41a5072b427ddacae8919a3cbffae6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9a7d2e0c015e6ffc4b6422f45b55c6d3b8e68e7ad1599916d13160b6c914cf9f
- MakerPaymentSpent: 2b6459aa1b559bd166383a7e7a35bf31b7f61f10f0854b675e93926f2ae7479c
f204a320327e441bf33f07a548882aac4684990bf5580dcb32fdeac8bf3103c5
Both payments are on their chains and locked to the same secret hash 955d72993a41a5072b427ddacae8919a3cbffae6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b86b4ebb664d73fc5006fa3238af61298990812ca9a62ee1acacaa6b4676bc8d
- TakerPaymentSent · TakerPaymentReceived: f204a320327e441bf33f07a548882aac4684990bf5580dcb32fdeac8bf3103c5
- TakerPaymentSpent: 76e469c6549e507092d167c5d5c81a7ad85dae53805dc269919c28fb2ce94f7e
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.