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.
aa3dc176112a5685ebc314e5e8f5860e811c0fef7c4fc092306ef2241307466e
Both payments are on their chains and locked to the same secret hash 5ef0cb81f4da2d7604356c8bc0f7f426d083538e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: aa3dc176112a5685ebc314e5e8f5860e811c0fef7c4fc092306ef2241307466e
- MakerPaymentSpent: 02a9342ed3012ce6ee8c3a11bf228194928861997e73a49fb19f0550c7b271d0
24e44c7b8dc74c30e6a9459569c7fcb4b9e553a86e7be7774ce20a547f679480
Both payments are on their chains and locked to the same secret hash 5ef0cb81f4da2d7604356c8bc0f7f426d083538e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: 4d849ddb821bfca9f5d95d8b8c2f954d93f9e1c2e4236f87a36317e69f8b16c7
- TakerPaymentSent: 24e44c7b8dc74c30e6a9459569c7fcb4b9e553a86e7be7774ce20a547f679480
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.