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.
d8c9fc7cde7101a5c1fc4e38d1925c5431fc3d862f327102f2ecc1c3ecb7c253
Both payments are on their chains and locked to the same secret hash e7f3448cae4a97ea36bf1dda67e83b6fb589eddf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d8c9fc7cde7101a5c1fc4e38d1925c5431fc3d862f327102f2ecc1c3ecb7c253
- MakerPaymentSpent: 37daa1db264c7f0197b7de1e08e295054caf66938a7fddceba7d90942e5be77f
0dd81f0bee64454626a847eaddd7e4a6af831455e8d6ad2f9c9e218346f43876
Both payments are on their chains and locked to the same secret hash e7f3448cae4a97ea36bf1dda67e83b6fb589eddf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d1148d68a8976b2930d27c731eee02b20329e7b9197cdb615636f1ba84011daa
- TakerPaymentSent · TakerPaymentReceived: 0dd81f0bee64454626a847eaddd7e4a6af831455e8d6ad2f9c9e218346f43876
- TakerPaymentSpent: d18a232b724038bd02e380c1e11bdcc4881db79c76914d20189ad2b26a5244e4
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.