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.
5807359a9935cb6f74be24a483f46e051a445d55774bfc3cb9bb0a422d97fa6d
Both payments are on their chains and locked to the same secret hash 10292541a04a6dd1932c1a2efc8249e4c1d0e100, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5807359a9935cb6f74be24a483f46e051a445d55774bfc3cb9bb0a422d97fa6d
- MakerPaymentSpent: 49b1d734a4d444270e46c09a83acc30b7eda52aacd1c7dfb351f56260537a7d8
246f3f77b3cd526d1df9c71d98c4e02710f5601b0cb972ee829984e34f3195aa
Both payments are on their chains and locked to the same secret hash 10292541a04a6dd1932c1a2efc8249e4c1d0e100, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 01e9518095d1dc95553a5423a56b840198ba6821d5faa61396488e7a486fbb98
- TakerPaymentSent · TakerPaymentReceived: 246f3f77b3cd526d1df9c71d98c4e02710f5601b0cb972ee829984e34f3195aa
- TakerPaymentSpent: ff8170ad9efb74b2d847c89a83794f91ba6ed4835b77d144690229b888f3cf29
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.