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.
4d241b27a52d1700997a6c3497d38383565482b6b72de52d0ef9361ab1acaa0b
Both payments are on their chains and locked to the same secret hash 320dcfb651a5fc9440b443df923eb979de249b78, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4d241b27a52d1700997a6c3497d38383565482b6b72de52d0ef9361ab1acaa0b
- MakerPaymentSpent: a97f133667dd98cd866108d83a88be7539f2763eef17b688d13b578a5113e035
22470e5a883abe874fc02178a259cfe1eb7df77b72d47ca057e6e40ca0885180
Both payments are on their chains and locked to the same secret hash 320dcfb651a5fc9440b443df923eb979de249b78, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a935756ddd53ff780814328f8fd9e9209ff7a66faa39b622b026282377b69400
- TakerPaymentSent · TakerPaymentReceived: 22470e5a883abe874fc02178a259cfe1eb7df77b72d47ca057e6e40ca0885180
- TakerPaymentSpent: 84e4434b2badca9d3b92178cd9ebbb4abb4e34c32e61114aa5a309a768e0343d
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.