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.
ab1c1b261f5d5ee9edcb3b86728c97bbf1f01483b659495291ff91947449172f
Both payments are on their chains and locked to the same secret hash 580cc14daca46b04c6e13959d547d1d40c0152d9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ab1c1b261f5d5ee9edcb3b86728c97bbf1f01483b659495291ff91947449172f
- MakerPaymentSpent: e7617098470d93201da4fdabe085259a29ee970585233691fe6a3f97f1f3a4a8
32b583bfcf74a71eaca5402249edc95ace6b1be7f4c757b4ca0dcfc195781bb2
Both payments are on their chains and locked to the same secret hash 580cc14daca46b04c6e13959d547d1d40c0152d9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 30c2c9205271af0036db522e89f43ebc40990d8cb1cedc5122fa159a1c941310
- TakerPaymentSent · TakerPaymentReceived: 32b583bfcf74a71eaca5402249edc95ace6b1be7f4c757b4ca0dcfc195781bb2
- TakerPaymentSpent: 8989aa3eb4a799ed55d393a7481d883dd2e69daea83b30fdcd0f831986afbf2d
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.