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.
d84c28e6e25eba6694dd2af374d2f80745a310faf323ec6d67c1f287ba548f30
Both payments are on their chains and locked to the same secret hash ddefe31022348e935b5b0ac07cbb0e596a7c77f0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: d84c28e6e25eba6694dd2af374d2f80745a310faf323ec6d67c1f287ba548f30
f5dc9014922fa3d455c01241f090e124c8cf209689bacf069de5ec6d56e7f5b8
Both payments are on their chains and locked to the same secret hash ddefe31022348e935b5b0ac07cbb0e596a7c77f0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: fda4e2b32a035281bcb5bc5b0376a594d766df3b4156210e6f9bc7f882aadc42
- TakerPaymentReceived: f5dc9014922fa3d455c01241f090e124c8cf209689bacf069de5ec6d56e7f5b8
- TakerPaymentSpent: eeaff9e6ca5075ecdc4dc0d7563da28906b40ff85ebc5e18099fd11099803b67
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.