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.
a1efe104c85f995ba3b3060dbeb1bfa769613e21388e2794b78e22d2b16afa3f
Both payments are on their chains and locked to the same secret hash 3cd2021de5bf53beb6cd9830cc88fc4c5742149a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a1efe104c85f995ba3b3060dbeb1bfa769613e21388e2794b78e22d2b16afa3f
- MakerPaymentSpent: 3ed40567008ff5db671d43854e2c89af544e4cef8eafbec25c0e0834587fa5a5
96478350c28904322d032ba41414176c1c5ba92bd42acbedee75fb1eb1a0457c
Both payments are on their chains and locked to the same secret hash 3cd2021de5bf53beb6cd9830cc88fc4c5742149a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d31414757b4ffe741ae912ee0f8a9f441aa89b3dce37620ca25be7642782ca97
- TakerPaymentSent · TakerPaymentReceived: 96478350c28904322d032ba41414176c1c5ba92bd42acbedee75fb1eb1a0457c
- TakerPaymentSpent: 3a9ba1f765f6b56093b070714b51c5c9a45d30b251c4de8987bdf62382c249e8
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.