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.
e7b18695da0f69b0130646c0c97a54ea83d3cd8aa6d6189454205e1c9abd5883
Both payments are on their chains and locked to the same secret hash 2dda899a3a988275a3f1f090ede0d8e5d95220ce, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e7b18695da0f69b0130646c0c97a54ea83d3cd8aa6d6189454205e1c9abd5883
- MakerPaymentSpent: 4626e5ac9684e3d3ed6b6fbf4f9f9c1ef61e3b2ecac56de8fdf7e66aafdcce61
b479c6c672cbfb0a3b86c6c5beba3764d2c7e50e41768da9aee386ceb45468bc
Both payments are on their chains and locked to the same secret hash 2dda899a3a988275a3f1f090ede0d8e5d95220ce, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 446d221d9a531ba8fbf631cb85b723db367fd40331913dbf0671017b8df3e7dd
- TakerPaymentSent · TakerPaymentReceived: b479c6c672cbfb0a3b86c6c5beba3764d2c7e50e41768da9aee386ceb45468bc
- TakerPaymentSpent: 9f0fedb87ee63a068328fbc603513441b472a5fdf5f6fa21b18b3bb1e45a480f
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.