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.
330325da0eb9be18a4119ea02f5c3b7b9b299318deb09dcc9c68bf9c541bce39
Both payments are on their chains and locked to the same secret hash 7f6a767714d5ebb830d71682ff8461616195a979, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 330325da0eb9be18a4119ea02f5c3b7b9b299318deb09dcc9c68bf9c541bce39
- MakerPaymentSpent: d9df0154c3a9ff500cfcbd330ec4bd3bff94c6e396de1f9836ad94fb55b76613
8a786037c76cb32f46465d597acc93bcb4c80af9ce2e54a65138375e816bc257
Both payments are on their chains and locked to the same secret hash 7f6a767714d5ebb830d71682ff8461616195a979, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ec6cf76bdb0bb2bf8911c7e816f2943410a21f25f4611f6c10441adce1a27423
- TakerPaymentSent · TakerPaymentReceived: 8a786037c76cb32f46465d597acc93bcb4c80af9ce2e54a65138375e816bc257
- TakerPaymentSpent: ac39a4841359a201193d6bfb56fc30e4bf4bb501d8f89027fa4099e3fc90c21b
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.