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.
949a82e06b029658ff8d5f0946399652a850f499844929708fba197f18a39d9f
Both payments are on their chains and locked to the same secret hash d3629152b34593fd233393787a652e1335e83d88, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 949a82e06b029658ff8d5f0946399652a850f499844929708fba197f18a39d9f
- MakerPaymentSpent: ddfc8136911b9ff14cbfc7fe24110c87a72e10a3c3a0b71581bd7710f7076b5e
d04ed540ee1624058877326f3fef473237ecddfe4e5a366ccaf64db82f4082bb
Both payments are on their chains and locked to the same secret hash d3629152b34593fd233393787a652e1335e83d88, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 605e7ac1f4db6f13f458ccfb05fb4f58f3e296b93907756033bb320bb08848d6
- TakerPaymentReceived · TakerPaymentSent: d04ed540ee1624058877326f3fef473237ecddfe4e5a366ccaf64db82f4082bb
- TakerPaymentSpent: 6e703d5b3b4c54f9ce4479dc8beb07577e2275f9df4cd5730db6ee3ab6975add
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.