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.
ddade8c1b380a626f6b2186df5eadcbe84410e3fe79c2f07d0fe133f991e070e
Both payments are on their chains and locked to the same secret hash dd1d8a9014f7a1e4b345368d2cc0918eea105850, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ddade8c1b380a626f6b2186df5eadcbe84410e3fe79c2f07d0fe133f991e070e
- MakerPaymentSpent: ca5bd77ae1f3f9d6f98042ad0ddd32f2cf221ccabdc3dbc61c75d012b12613c1
d79cbfe55ae5bcd94498e3289820c2cf44e904b485f1fffae0ab55d12637193b
Both payments are on their chains and locked to the same secret hash dd1d8a9014f7a1e4b345368d2cc0918eea105850, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8aa8a0ea69b5383c9f8058fa65f5ac15decfaf8fccf1b1b6ccbfd239654160d7
- TakerPaymentSent · TakerPaymentReceived: d79cbfe55ae5bcd94498e3289820c2cf44e904b485f1fffae0ab55d12637193b
- TakerPaymentSpent: e2aa8dd8e741a247fb26258280b7e60e816f0bcb325c390fff4241e9761c2bc0
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.