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.
ff567126bc8353fa400a0ded0bf28db0827bb9841177e3bfccc0c48c917df4af
Both payments are on their chains and locked to the same secret hash e02f47ab8c6832192dfeae72299749f9bdac6f55, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ff567126bc8353fa400a0ded0bf28db0827bb9841177e3bfccc0c48c917df4af
- MakerPaymentSpent: 0e80ba563d7ef86223ff4115a7b1c916360b609abdfc1fe363e4282a12ec4b4e
f99c4dfe5591802d2cd85c9c7319ca7ab6e443ad1d17b7906c297ec37c247cac
Both payments are on their chains and locked to the same secret hash e02f47ab8c6832192dfeae72299749f9bdac6f55, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3c552ba2de36263aac4d7cbe9e75cfc0376c74ac393b866824cd01e2224662d6
- TakerPaymentSent · TakerPaymentReceived: f99c4dfe5591802d2cd85c9c7319ca7ab6e443ad1d17b7906c297ec37c247cac
- TakerPaymentSpent: a49f1dba16d0915c39fe95455aa15b5e5cd8cea74c57fe4073f80e51eb5b9125
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.