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.
45bf899ed48521e34af7c16b218d30fae0c27ed1818b7d0687b77eefd787509f
Both payments are on their chains and locked to the same secret hash 3bb3b4fd34457ebbca018a9f838ed95552ce4630, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 45bf899ed48521e34af7c16b218d30fae0c27ed1818b7d0687b77eefd787509f
- MakerPaymentSpent: ba0cd7b3239bd0e00fe20501ad299327052f55fc195368d0b16f8a849b8c9d90
4168f9ea84d23ada0eebf0847144756dc80adb454911230f2d5f706ac062e325
Both payments are on their chains and locked to the same secret hash 3bb3b4fd34457ebbca018a9f838ed95552ce4630, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9e8d3f93f350507beb362ed66611cb97059f92d71dea25c0317fc95893d925c8
- TakerPaymentSent · TakerPaymentReceived: 4168f9ea84d23ada0eebf0847144756dc80adb454911230f2d5f706ac062e325
- TakerPaymentSpent: fd5be4dae80fabe599b374cbbfa8862726b4af44a1cc1300adf788f79adb44be
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.