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.
916c1dd0e6d979b123f18d9276297afdca8a69ff40e53a7f2c633aec17c2f978
Both payments are on their chains and locked to the same secret hash 8f6e08ed182e7e3b3561d893979ca28175dd1c75, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 916c1dd0e6d979b123f18d9276297afdca8a69ff40e53a7f2c633aec17c2f978
e47314d6792613efd925e468d0f1e7b874454807d864caf8bcc6a3c5e1092a98
Both payments are on their chains and locked to the same secret hash 8f6e08ed182e7e3b3561d893979ca28175dd1c75, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 11f41014c10ab6513c2e3396c4eff782d0c276b30af4d80801b8268d8aadbe8b
- TakerPaymentReceived: e47314d6792613efd925e468d0f1e7b874454807d864caf8bcc6a3c5e1092a98
- TakerPaymentSpent: 99799e6f8136ab077907e0a06ff3ce18dfdf42b84ac4f6080fee7d1f7acdc0a4
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.