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.
cfce5472c424d17f0c5d69ee3bcfdffe055b1dc1716c78065fc438c9c46786fa
Both payments are on their chains and locked to the same secret hash abe0d3644ee4789073649c5fc200ef325ec258f0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cfce5472c424d17f0c5d69ee3bcfdffe055b1dc1716c78065fc438c9c46786fa
- MakerPaymentSpent: 2b2d05594ae274ee4d977ba2f6787fb22e547631e411798aefdd5eb10b8e58d3
23ed013368980762ac3f54caa9f3530055d94388b3d14e7ebc667c5ac0bd3f35
Both payments are on their chains and locked to the same secret hash abe0d3644ee4789073649c5fc200ef325ec258f0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3a35ffcc792adbfc50bdaaaa25e3ec4264b3d9103247540dd79502aafe4a319b
- TakerPaymentSent · TakerPaymentReceived: 23ed013368980762ac3f54caa9f3530055d94388b3d14e7ebc667c5ac0bd3f35
- TakerPaymentSpent: 7c602e7e444c21eefa06891a88f918de38f6c4fa756eb3952678b138c91630c0
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.