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.
afd6e286e631aeef2ce945a270a970d5927d1ac8186883eec9f005a2757c8d61
Both payments are on their chains and locked to the same secret hash bd9146c8c82b921667e37673ef47a03fb025906e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: afd6e286e631aeef2ce945a270a970d5927d1ac8186883eec9f005a2757c8d61
- MakerPaymentSpent: b11e2a66cdf4137ed507600baaf58407b034e460947ea7d46d184f820526ad9f
cc4237ae88cd4cce58269767919afde4627e73f1166d58332105bb17ec732f23
Both payments are on their chains and locked to the same secret hash bd9146c8c82b921667e37673ef47a03fb025906e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fe3dabfbe4b9141af95e3fa53b87d2e0adb9ad50f971146a3af48f7ac9dcdf62
- TakerPaymentSent · TakerPaymentReceived: cc4237ae88cd4cce58269767919afde4627e73f1166d58332105bb17ec732f23
- TakerPaymentSpent: fc00eb58f180cc193680211086f1588043a5281d5b825100d31fa5cf33b40d91
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.