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.
246519a5eff0252d25908b2f1ab99a16c2a2d5dccffe19dd7bc4189a62a7be4a
no server returned transaction 246519a5eff0…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentReceived · MakerPaymentSent: 246519a5eff0252d25908b2f1ab99a16c2a2d5dccffe19dd7bc4189a62a7be4a
- MakerPaymentSpent: 0d170a0a54cb163a6ddc6ad60b09eb2074f9905908c4f41622d239c5b232abc9
b6d81172c1aa3a267c97247bace32ac30717197107a959227a65a3552b4224ab
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: acaf865639f1a59cc276521e11dad5fa1b683636025a501ee29d0d258aa4a0e1
- TakerPaymentSent · TakerPaymentReceived: b6d81172c1aa3a267c97247bace32ac30717197107a959227a65a3552b4224ab
- TakerPaymentSpent: 4ddc40f40ee5dea6a3b64e1776ba8dd7aab6e0541ee70c6dc75fb0b654e4acff
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.