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.
30f61311353d06cf73c06a85a8bdde11d0c9313c337ed9085eb392b5f10e7c87
Both payments are on their chains and locked to the same secret hash 82fd26c59dce485ec98771d787edd13ab85a48bd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 30f61311353d06cf73c06a85a8bdde11d0c9313c337ed9085eb392b5f10e7c87
- MakerPaymentSpent: c67e57b68199a830ed665c8640870ba3fdaeef71852052a0edaa9af178e11b6a
f8718cb9aa3d21a64cc3e360b11782d6ad9c6e16289bd8fee5e7a879d1ab7cc5
Both payments are on their chains and locked to the same secret hash 82fd26c59dce485ec98771d787edd13ab85a48bd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 29f08cf9bdf4b890147e562ea86c8b829a1bf33403a86746e26130809b83eed2
- TakerPaymentSent · TakerPaymentReceived: f8718cb9aa3d21a64cc3e360b11782d6ad9c6e16289bd8fee5e7a879d1ab7cc5
- TakerPaymentSpent: d398eed51008bd29b52093c2de9ec34c35c5dbf94d5575632bc8925449461472
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.