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.
d009e0304ea6ab1eb2066ae0143b19324a44c0c6d188f5ea64da6098143a1bab
Both payments are on their chains and locked to the same secret hash b4c16554a9521f5110d9a6bad2193b98b285d576, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d009e0304ea6ab1eb2066ae0143b19324a44c0c6d188f5ea64da6098143a1bab
- MakerPaymentSpent: 3a1f34109d33b5e133bcfaf31c4c2d49cf1e75e4cb40a56034e30a6de8186d78
69cb0287707a8ead7753e6c884a33337ed3c95462c0c3ab209dfb0bbe495b9cb
Both payments are on their chains and locked to the same secret hash b4c16554a9521f5110d9a6bad2193b98b285d576, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 79d76f4ca9d4e9383ac7cd0e6a4ea11df4d70d48fa6b626fcde76cb4d2865946
- TakerPaymentSent · TakerPaymentReceived: 69cb0287707a8ead7753e6c884a33337ed3c95462c0c3ab209dfb0bbe495b9cb
- TakerPaymentSpent: d1ef9b97648b495359eea17a1faad75bca6852cb88e04c92cbe0b8d696954deb
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.