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.
4ee0e6c8915cb453cbd8c6a1296fd2056b997576d4a830255e176fb1df7e0793
Both payments are on their chains and locked to the same secret hash c9ad12870d1c4c0c9bc4ffa894331e16565c325e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4ee0e6c8915cb453cbd8c6a1296fd2056b997576d4a830255e176fb1df7e0793
- MakerPaymentSpent: f4cd56d7b52b144c2e6d3011f446a8e06e67a043eea84e377b0fa821cd383dac
be7a57e519009cf4507ec5d019de66e9eb671baa9a1bea704b663b2009223e56
Both payments are on their chains and locked to the same secret hash c9ad12870d1c4c0c9bc4ffa894331e16565c325e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b5e159d3cb06c378b997ed10753ad7314076c6514bc6824403239118f48f3a05
- TakerPaymentSent · TakerPaymentReceived: be7a57e519009cf4507ec5d019de66e9eb671baa9a1bea704b663b2009223e56
- TakerPaymentSpent: 08f71d6ad4e29d5cfd0c76f9522d5b936f39a9c8f5ec657b827adcc6ce76fd02
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.