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.
9a7077290a48227f61ca201f84734e53b9199b77c239e2288b3e3635468285b2
Both payments are on their chains and locked to the same secret hash a0532f37b32ec75a17a6adcbc88411a304768840, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9a7077290a48227f61ca201f84734e53b9199b77c239e2288b3e3635468285b2
- MakerPaymentSpent: 50ff7e7be1ff46aef27d8af50b664066b770cfba9b5bce73d43e36c849ae80f9
08e552edc62db96c3bf9321f3c44bba052c9d688f460e05096f29179548912ec
Both payments are on their chains and locked to the same secret hash a0532f37b32ec75a17a6adcbc88411a304768840, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 942365c51850b98a00204de4810f39058b2c6a369b748a9fc3c06300d6c61886
- TakerPaymentSent · TakerPaymentReceived: 08e552edc62db96c3bf9321f3c44bba052c9d688f460e05096f29179548912ec
- TakerPaymentSpent: cacb3042e02ef563ce627b048974fcea874ca3269f998d05826f7e2c01c5b06d
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.