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.
3fc423d783484e57852cb1f0ef518ba970369501ee9dd33c1181ce413f6dac7e
Both payments are on their chains and locked to the same secret hash f0608871bfeee57c076f51e5adaa2cc6ebaa73ac, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3fc423d783484e57852cb1f0ef518ba970369501ee9dd33c1181ce413f6dac7e
- MakerPaymentSpent: 014e79136a11fa894d8808891619ba1952890c72a5bfabc9423c7a10f64d1fe9
230654e3bf58d7675c69e09330dabd824131218cf4fbfb3c89d16d7d975c921e
Both payments are on their chains and locked to the same secret hash f0608871bfeee57c076f51e5adaa2cc6ebaa73ac, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6fb062e99dc82dca0ee2043f309e0ce5451552a9412366f28b02f27067d2cdea
- TakerPaymentSent · TakerPaymentReceived: 230654e3bf58d7675c69e09330dabd824131218cf4fbfb3c89d16d7d975c921e
- TakerPaymentSpent: 3315449ff3181ba3c069347272df03073cd9ab2be27d1e84ba0c3ecab89cff0f
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.