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.
0d68f50cb7b0408ecd39f6fa79f215b5dec5c043df6daedd747afd7df657c4aa
Both payments are on their chains and locked to the same secret hash 52b02d745249fc6c2823665ce7f0dfd60e3cd5f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 0d68f50cb7b0408ecd39f6fa79f215b5dec5c043df6daedd747afd7df657c4aa
ae692dfb6bf3cb2516493c9505b2358e5e1608a61c391f2a3d5d964c96844e14
Both payments are on their chains and locked to the same secret hash 52b02d745249fc6c2823665ce7f0dfd60e3cd5f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentReceived: ae692dfb6bf3cb2516493c9505b2358e5e1608a61c391f2a3d5d964c96844e14
- TakerPaymentSpent: f6e5c16660a055950afbf94a9c452015f581de77542376666beef3f9c0618550
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.