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.
d1ba7a11314cf79d24d55eda4cf758a263ce93d578e0ddd909eae7c267165c29
Both payments are on their chains and locked to the same secret hash 218c9f0b9545747a3924562017f0427556a7ad46, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d1ba7a11314cf79d24d55eda4cf758a263ce93d578e0ddd909eae7c267165c29
- MakerPaymentSpent: 2c6fd8e8f13c8151462a97d51a5c5cae42fa0ed3cb1122f07bc0469d536d4595
bc7b66856447405aca0f4e07bcbec49992ffe8919c0c66263786f09f41efaeb8
Both payments are on their chains and locked to the same secret hash 218c9f0b9545747a3924562017f0427556a7ad46, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b0dfbd5b10b33bef795e6263742c6c85cdd0a1e50748bf27f8a13632dff72c3c
- TakerPaymentSent · TakerPaymentReceived: bc7b66856447405aca0f4e07bcbec49992ffe8919c0c66263786f09f41efaeb8
- TakerPaymentSpent: 333e9df567751fd620ffed4aa0ea04361e175a461e67dc207a9bdabe468cc7f9
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.