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.
ce1a72a067cd272115cdc75f78ca6fd239eed69606f00937e69a6789c92d5d80
Both payments are on their chains and locked to the same secret hash 6c93544e512ebb2c5b918d2f04974e455721052e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ce1a72a067cd272115cdc75f78ca6fd239eed69606f00937e69a6789c92d5d80
- MakerPaymentSpent: 90c935c1a531ba54279459c2f0b19ae416c44b8fc0e8bd667457c70f500a0d3c
10fca65d237b677ea386b74fbbd1bcb3db6ed5d5678b51cddc40114c6037a0d2
Both payments are on their chains and locked to the same secret hash 6c93544e512ebb2c5b918d2f04974e455721052e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e50ff6ad425e550ca3c07de9159acaf1a22618aac6da8e28fe1f953afeaa6552
- TakerPaymentSent · TakerPaymentReceived: 10fca65d237b677ea386b74fbbd1bcb3db6ed5d5678b51cddc40114c6037a0d2
- TakerPaymentSpent: 85585dfd0ddd83025c9d6cad63dddf85f416ae115e32a0db2f646de384f153a3
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.