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.
d89477e9d6dd22d39197d3dcaf368e39706e26f3bc73525b2bee1b2d86bed8e9
Both payments are on their chains and locked to the same secret hash 555d9d3614f27e3842c8f8e7793b9377aa32b0ef, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: d89477e9d6dd22d39197d3dcaf368e39706e26f3bc73525b2bee1b2d86bed8e9
5d4f95bdd22adcae231739ac606d3298239a4979b016f5ab6228fd0486f85f15
Both payments are on their chains and locked to the same secret hash 555d9d3614f27e3842c8f8e7793b9377aa32b0ef, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: c2f0a2e2c8202c7b51383817ff0716e2bdc401a970ff074b3f40a6739172c69c
- TakerPaymentReceived: 5d4f95bdd22adcae231739ac606d3298239a4979b016f5ab6228fd0486f85f15
- TakerPaymentSpent: 2eed981ae93a094c9eff2fad5e97aae46d07091d4e82ebc6f97a5a764463c24e
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.