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.
833d9ed101dc807fcb1cd8b1b3b232cd3e47e82fd01dee9f561657dc5976bfbb
Both payments are on their chains and locked to the same secret hash d81bae8a0fa4c6696f0eb8b902a97201efdf2c1b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 833d9ed101dc807fcb1cd8b1b3b232cd3e47e82fd01dee9f561657dc5976bfbb
349d7a460978fc07f5f260c3f0625b301fd30c68b84dfdd45f58bfdc05de3882
Both payments are on their chains and locked to the same secret hash d81bae8a0fa4c6696f0eb8b902a97201efdf2c1b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: feef7c60c70d3d2bca50c5f0693c7fbc1f4d1a3e2d8afd5fc84eb78b5b0b780b
- TakerPaymentReceived: 349d7a460978fc07f5f260c3f0625b301fd30c68b84dfdd45f58bfdc05de3882
- TakerPaymentSpent: 0ee4e80528be729161a4d15251edb8808ca2f788c149c1237a95d56cb7868f51
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.