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.
411118208686986ab77d00820f88802f4743e1098bca31ee248b13ba9a37b7d2
Both payments are on their chains and locked to the same secret hash 1906f9ab443ab9a48f6337458d3705662173f1fc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 411118208686986ab77d00820f88802f4743e1098bca31ee248b13ba9a37b7d2
- MakerPaymentSpent: 35105f0782779d5eac8daef87a6991c0e99d501433cbd527e79087b440c61ccf
fadd38ebbc25727b4ffbc599a9b6ffc6ddf2859c9557e8cfea128894b02412c0
Both payments are on their chains and locked to the same secret hash 1906f9ab443ab9a48f6337458d3705662173f1fc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 19795731921f68535b092cef3d3d6113048f559df97387e8d342ec979ac67ce5
- TakerPaymentSent · TakerPaymentReceived: fadd38ebbc25727b4ffbc599a9b6ffc6ddf2859c9557e8cfea128894b02412c0
- TakerPaymentSpent: 08a65fce8719ffdf776804bc645ba2dc12879c9a2bcb653432ac80212a708d06
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.