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.
c6c3dfcfb5b992a298a1ae73c892664cfdeda101881d54c71340b9280c711995
Both payments are on their chains and locked to the same secret hash fd2e318b3581aea7b25bb6b4064a424b895f5db8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c6c3dfcfb5b992a298a1ae73c892664cfdeda101881d54c71340b9280c711995
18e6d42c2243396d4b742d6c1ccd60103670be7d63ca8f477721a078df551fa5
Both payments are on their chains and locked to the same secret hash fd2e318b3581aea7b25bb6b4064a424b895f5db8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: dd014de11a99320453049b3779c33a6f29103b6a0d4770f765751fc3fa9a738d
- TakerPaymentReceived: 18e6d42c2243396d4b742d6c1ccd60103670be7d63ca8f477721a078df551fa5
- TakerPaymentSpent: f7dcc51cea0f8e059ec444802846a438ab4dee15866107db1dcc45c346784aeb
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.