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.
46f5060824b4402e6105b20d0282e2c324b1a4198e1e8cfa9c9019cb9b0ecd00
Both payments are on their chains and locked to the same secret hash 77040d653923dab37b5a73bf81b8ebcb83d5cfe0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 46f5060824b4402e6105b20d0282e2c324b1a4198e1e8cfa9c9019cb9b0ecd00
- MakerPaymentSpent: b2f2fee093428fff365308b46df80e2384cf74b1d3714be8cacf4b78e67729bf
bc83cc72a37f285370080fb111b43bef172d9ee9bff31d83263ef24fa5f57c9b
Both payments are on their chains and locked to the same secret hash 77040d653923dab37b5a73bf81b8ebcb83d5cfe0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6665704a74220c43871953c7d020ecc24fc7344456234886cb4438d040cf6be8
- TakerPaymentSent · TakerPaymentReceived: bc83cc72a37f285370080fb111b43bef172d9ee9bff31d83263ef24fa5f57c9b
- TakerPaymentSpent: bb11f8d83de33314465f4542ee1c5056467119c682a586f54809f9147b11d192
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.