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.
e9e174a5901ec91a77c95c254c332fd8eb528c84b5d887d54132293bde25e1ec
Both payments are on their chains and locked to the same secret hash 39df2799fe1d008eaa70bfb0b54a910e923e8115, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e9e174a5901ec91a77c95c254c332fd8eb528c84b5d887d54132293bde25e1ec
- MakerPaymentSpent: 71817dedd4fc25b2cb25de1e582045651c0ffdea15a6e16d1fc3a1cd967cd2ed
27008563fa2e459ca190735ab80cf1353b78f9e775d5ebce1e75884bb55b79cb
Both payments are on their chains and locked to the same secret hash 39df2799fe1d008eaa70bfb0b54a910e923e8115, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8e13812ef99e61c8b4682ad5fc98cd4ccb85e40afe1da88db52dad2ecb385eaf
- TakerPaymentSent · TakerPaymentReceived: 27008563fa2e459ca190735ab80cf1353b78f9e775d5ebce1e75884bb55b79cb
- TakerPaymentSpent: da5209fc138bd35df51978bf212f3c937f7b3dcb36a674ee6caae77bef5d3cd1
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.