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.
c09dd43eb1b76645cc1b19c32b559b43a2247aad57d9879864278d92763cca9a
Both payments are on their chains and locked to the same secret hash 6e74a72c44e68cbb0c6374e5bd28581ec4d5ea2a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c09dd43eb1b76645cc1b19c32b559b43a2247aad57d9879864278d92763cca9a
- MakerPaymentSpent: 92ef9db4f7bcdc54946b382cc4fc4be1c8cf9537005b4be839fd4af7e7224587
dfe72542231ee8487f2bcf30ed1b5a27981dd84841557553fe9ff354ced23709
Both payments are on their chains and locked to the same secret hash 6e74a72c44e68cbb0c6374e5bd28581ec4d5ea2a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dd3226a2a080acde59e46bcd107bd70bc0f577a2966308a794a9b9850e0dfd62
- TakerPaymentSent · TakerPaymentReceived: dfe72542231ee8487f2bcf30ed1b5a27981dd84841557553fe9ff354ced23709
- TakerPaymentSpent: 4c2433612c3b04c3b66f85bc56640940122ffc2f5206f37a96bb3a788c1bebee
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.