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.
cb9ab89361f2773cf21e7a8ecf7067de1835c525450b379b9a858c976cb0fc0c
Both payments are on their chains and locked to the same secret hash 5d003d6a98eda92e79facec9ddcba2fb2362be58, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cb9ab89361f2773cf21e7a8ecf7067de1835c525450b379b9a858c976cb0fc0c
- MakerPaymentSpent: a860ec02acfa6acbc8e17af6c3f45da9f578791d618172c37ba193e5ebe3570c
bd6e0b5ac13096574fa13404f0a1f7d6f526bbf2af1bff7019b83b3b76e8a9a5
Both payments are on their chains and locked to the same secret hash 5d003d6a98eda92e79facec9ddcba2fb2362be58, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d408ff9822491c62d53861eba9d628a5bc2939b4172eecb85c3ba913cf38f7aa
- TakerPaymentSent · TakerPaymentReceived: bd6e0b5ac13096574fa13404f0a1f7d6f526bbf2af1bff7019b83b3b76e8a9a5
- TakerPaymentSpent: b6ddc5eb82d30eb2f334904e2e9793c57207e3dd926a2fd6e74fb5dba13c648e
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.