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.
50eafbda8cffa5ac199fc5b0771e14536e7facc724bc7c7ba229039bbdc342e8
Both payments are on their chains and locked to the same secret hash 89c0c56640b8c2d852b2ff9acffebbd25ca59972, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 50eafbda8cffa5ac199fc5b0771e14536e7facc724bc7c7ba229039bbdc342e8
- MakerPaymentSpent: 57918f111634981c87ca68e25742662271324cdf3a1f39260f1068c2cbb98d27
cadd2d3b4aed434666d59b3ff4fb4339aae986893149537a66ed6bb8dcaa6464
Both payments are on their chains and locked to the same secret hash 89c0c56640b8c2d852b2ff9acffebbd25ca59972, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0b3c67ab4be7a71d3cfd2114f2de34308dff68b3f4c4773767541bf11b2845bd
- TakerPaymentSent · TakerPaymentReceived: cadd2d3b4aed434666d59b3ff4fb4339aae986893149537a66ed6bb8dcaa6464
- TakerPaymentSpent: 72d1650b06d82bab694054c6a10b84706689fd490570020c2836a5715020875d
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.