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.
d77bb47fe60a4af6003cd43e334cdfe80c9079a0a2ac97b7551ee9c0bdb6a9b8
Both payments are on their chains and locked to the same secret hash 8dc0c47406b890cf71984590381700a4a9052b9a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: d77bb47fe60a4af6003cd43e334cdfe80c9079a0a2ac97b7551ee9c0bdb6a9b8
2cf133464f7f021fd87a3fabf8e06be9a6bf4b3d1e8e177b9ce30fd4b272e001
Both payments are on their chains and locked to the same secret hash 8dc0c47406b890cf71984590381700a4a9052b9a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 6a203b2bde22b30c3f6f00a496ed25c8386a400faf0d7dbadfec4c399cab6a17
- TakerPaymentReceived: 2cf133464f7f021fd87a3fabf8e06be9a6bf4b3d1e8e177b9ce30fd4b272e001
- TakerPaymentSpent: 04577f01695c66819abe531f7c4e551473e9626648b44e8d7e75fc3bed72efd0
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.