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.
321a0213cfb683d8999739e6bfc4f7d4133355d5141f59dac8c9dabc3f0cf099
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 321a0213cfb683d8999739e6bfc4f7d4133355d5141f59dac8c9dabc3f0cf099
- MakerPaymentSpent: 426b55c26650ee3b9a0a89c1110403f6f463960ba0d743f02fb13958029e6ee8
dbd04ddb9cc05cab113170139311d1e70ec4eca1f8a809927d2e62c7e7791881
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 15e800751fa425fb1666b14c92db9739a7721b46b9247c2cd3676f5cd725c968
- TakerPaymentSent · TakerPaymentReceived: dbd04ddb9cc05cab113170139311d1e70ec4eca1f8a809927d2e62c7e7791881
- TakerPaymentSpent: a4231a2ec16d78d656912ef41f575d9abd56e68db0672ee7bebeb20d35189e6d
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.