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.
420dc8439286c3db93f8bded0c4268e002975c75b26ed90986829a22264cb7b8
Both payments are on their chains and locked to the same secret hash d4eff35c8315043e8766ac3bdf9fa77d92f95724, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 420dc8439286c3db93f8bded0c4268e002975c75b26ed90986829a22264cb7b8
- MakerPaymentSpent: 72d4ae5767b69695068e3118d54b192b4ed55f9c8e1d610430138e69f689a333
7c43789fee2cec74a0c6614aa996887f4ed310e0656eb11bf998d3bf529dffe6
Both payments are on their chains and locked to the same secret hash d4eff35c8315043e8766ac3bdf9fa77d92f95724, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7cc071b95cc0c34f506827aee7abc4eab96bb09ebe21d48f1b31e4b243580211
- TakerPaymentSent · TakerPaymentReceived: 7c43789fee2cec74a0c6614aa996887f4ed310e0656eb11bf998d3bf529dffe6
- TakerPaymentSpent: 2e3d8fe4169bb1981654057bf9bdc47bf26f61ca90eaa4840a133901d39b65ea
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.