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.
479941a56384e1dc8879cac023e47dce93987dd25b1025bfedd52604a9753441
Both payments are on their chains and locked to the same secret hash 8f6548d2c6489ea37fcfd54d759549e199d2b35b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: 479941a56384e1dc8879cac023e47dce93987dd25b1025bfedd52604a9753441
- MakerPaymentSpent: e3a4e2eb10d01a838b2236830bbcb6117918248b47d4c24202380e65cc7edccb
55bfd66ea389db4b9d6eedaa71d5ece9e59bf6ce9f32eca93fc74ec847310602
Both payments are on their chains and locked to the same secret hash 8f6548d2c6489ea37fcfd54d759549e199d2b35b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: cd232ce81dc001bff61a4df09d9038bb16434118fcfdf4372c61a483ac19efa1
- TakerPaymentSent: 55bfd66ea389db4b9d6eedaa71d5ece9e59bf6ce9f32eca93fc74ec847310602
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.