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.
ffa2c796fc1300c46030394fa7127772e0f21edce5128c99eacaf332a07c8548
Both payments are on their chains and locked to the same secret hash 63361b34c7aaac2ea638255e669e2b308182f70e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ffa2c796fc1300c46030394fa7127772e0f21edce5128c99eacaf332a07c8548
- MakerPaymentSpent: c2fa869d71405e1b66072e10fa67152c36b0c7f7aaaeed662adc8498d9e27070
cf0473d16ba828511be6c24376d73f81125484b979d1e1879726b264c198662c
Both payments are on their chains and locked to the same secret hash 63361b34c7aaac2ea638255e669e2b308182f70e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1cc022f2899e46da44a853d66ab99d5d526ca89141fb622621bd81b1fe4879d9
- TakerPaymentSent · TakerPaymentReceived: cf0473d16ba828511be6c24376d73f81125484b979d1e1879726b264c198662c
- TakerPaymentSpent: 2dc6fa092954a7c7136f0870c9e5d5d35fde7378efc004bb1609765f0162782f
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.