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.
26b9a2625abef2de44123c400590588a767aeb86d4943edd84181d5bee21b89b
Both payments are on their chains and locked to the same secret hash 461038716530beadaa40e44ab613e28fa05be597, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 26b9a2625abef2de44123c400590588a767aeb86d4943edd84181d5bee21b89b
- MakerPaymentSpent: 318090f4854aa981075a45246c368fa30a7cdf9a83c4629eef2883615b439a20
2bfd0bf46f746f4789c2726cc310b714a5d3b82be5544e5a2fb4871d3dd3db38
Both payments are on their chains and locked to the same secret hash 461038716530beadaa40e44ab613e28fa05be597, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a8f665360f717c33bffe738e4dbf570c5afaea1272be5cbea3dfb1a96393facd
- TakerPaymentSent · TakerPaymentReceived: 2bfd0bf46f746f4789c2726cc310b714a5d3b82be5544e5a2fb4871d3dd3db38
- TakerPaymentSpent: 6014b42db4c972c951351ee2930b65df958b10e8f0391fc3f8550df945860815
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.