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.
52703a1d0fca9e2fb58c0a04c1600954271aa8b3f212a5179ba14360bda1dce4
Both payments are on their chains and locked to the same secret hash 0843d6f421cd516d1cb1b9697fe62cb935b494f0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 52703a1d0fca9e2fb58c0a04c1600954271aa8b3f212a5179ba14360bda1dce4
- MakerPaymentSpent: 17182ac639758f3a3322e0d30f870b76d57ee868bfbcf6a63581c40e1bc2ee30
d7b9ce49b13df8bfd591e03776dcdeb04549df619dd781fb6fd9be8cdfc9dcb5
Both payments are on their chains and locked to the same secret hash 0843d6f421cd516d1cb1b9697fe62cb935b494f0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f50a4815e498fc1be94da2bbdf5bad91d90fee61cc12dcec479fa8cb6e92bdbf
- TakerPaymentSent · TakerPaymentReceived: d7b9ce49b13df8bfd591e03776dcdeb04549df619dd781fb6fd9be8cdfc9dcb5
- TakerPaymentSpent: 79dcb85f3687ce2338767669bc8964eae6e8934c97f9b709ca69aeb3c60e8728
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.