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.
c57fd9bcff20153e27cda5e1f3429d7ea5108f7a18b6aae2b29fd71080e93df2
Both payments are on their chains and locked to the same secret hash b3e30425edb364f110797070711fc0cad7768543, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c57fd9bcff20153e27cda5e1f3429d7ea5108f7a18b6aae2b29fd71080e93df2
- MakerPaymentSpent: 964fa511f0c9202bff2cedde8fc1d277ae3d6ac79b6fbc2bd3e61fd7ff3d1b66
af8e6ef2fd1f9abc59f1d7a79db2d27a8609912cb8d3d581d5c9b508d44a42fe
Both payments are on their chains and locked to the same secret hash b3e30425edb364f110797070711fc0cad7768543, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2f03992925b9f81803e075876de3a37804c4be606e4be91fd3a9ff141cc83660
- TakerPaymentSent · TakerPaymentReceived: af8e6ef2fd1f9abc59f1d7a79db2d27a8609912cb8d3d581d5c9b508d44a42fe
- TakerPaymentSpent: 21dbb3a6877a0d30cf94ae24390ee9e1a0ee14381d0b9ef6496f2f2cb5c23f02
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.