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.
ad0bb667e5a3ceff6eb4b5ac3195490680c6917f7b448a8fd271daad786fc28d
Both payments are on their chains and locked to the same secret hash cfe08a10ef986f701c26dc14522e68e080f6f361, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ad0bb667e5a3ceff6eb4b5ac3195490680c6917f7b448a8fd271daad786fc28d
- MakerPaymentSpent: 7dcadb642f25d3b794be24aba94b8a8aded33cfb9397ca4451d86ebdd823dd1c
c953dabc803046f46de2053b9ab1d922b7c155302040911ebdbe6ca2efe88370
Both payments are on their chains and locked to the same secret hash cfe08a10ef986f701c26dc14522e68e080f6f361, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 370fa4935a855d6580c8c68de0803ee270c9ae65f62dbd077b10d503f334490f
- TakerPaymentSent · TakerPaymentReceived: c953dabc803046f46de2053b9ab1d922b7c155302040911ebdbe6ca2efe88370
- TakerPaymentSpent: 9cd7b347912e67a77e9470c551d6a2a64fb2c5f6b0f4a7550d62cbcf05dd3b82
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.