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.
f8a71d318774d7a869d79465e9456f8874cfc734443076535d14bbb4e0d68429
no server returned transaction f8a71d318774…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent · MakerPaymentReceived: f8a71d318774d7a869d79465e9456f8874cfc734443076535d14bbb4e0d68429
- MakerPaymentSpent: 62ff6a8a9820a4dee15268274750d11bc146a3d02892fb556694c0537f00af4b
456eff385c8f9ddfc829f4f89e3198452ca964e039e96d39f22c4642109714a3
confirmed on-chain, calling the swap contract, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 8de18a8d7a85eb3e5106768341f6a8f58fbb1c6177aacf64a1bb43ddc10ff173
- TakerPaymentSent · TakerPaymentReceived: 456eff385c8f9ddfc829f4f89e3198452ca964e039e96d39f22c4642109714a3
- TakerPaymentSpent: f0b4c79171c8a90e3c29a2beddd8063df5384af45f3fa6ec2078a79c157776a1
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.