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.
afdb848b9884b68014dfcf32694e3a3e50ce148e0dc2427b07f93d6ca8db75ff
Both payments are on their chains and locked to the same secret hash 70dfc8f1cb50b0dd8a61f2fe29461f72674bbfd7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: afdb848b9884b68014dfcf32694e3a3e50ce148e0dc2427b07f93d6ca8db75ff
- MakerPaymentSpent: 9602694050e5c3153d71fe07677e56672c9540cc451628a030c3c7fde209d220
5ed54387ba453d7e67cc7a8b927798b405bb2a85b4f574d860e5f5156a1e908f
Both payments are on their chains and locked to the same secret hash 70dfc8f1cb50b0dd8a61f2fe29461f72674bbfd7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 863ff0cc581e3b316f93db410c9db49e1c4aa6ecbd41361e9eb7f2f520b350a4
- TakerPaymentSent · TakerPaymentReceived: 5ed54387ba453d7e67cc7a8b927798b405bb2a85b4f574d860e5f5156a1e908f
- TakerPaymentSpent: 8202221f9c29ca0471fb74dc8225a71921b5625f4f9cedf8a5156f76f0ae6925
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.