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.
499b0e378daba36ba69de1ee29b95fe86c817b1ce49c45b2fc1d1e7338cc1298
no server returned transaction 499b0e378dab…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent · MakerPaymentReceived: 499b0e378daba36ba69de1ee29b95fe86c817b1ce49c45b2fc1d1e7338cc1298
- MakerPaymentSpent: d5945a6a43ff0c9b6530927ca32d5f5b57b3f1eb9d8cf820c62113a901d182cf
d688a0c4204cd8be95cd5e969a0679136a3d54b6fc97f754c745fb9b072d2629
confirmed on-chain, calling the swap contract, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 724355f94e3bd3632ce0bdf75c510bf84ac42d72947a5c07fb900d2ebeb76715
- TakerPaymentSent · TakerPaymentReceived: d688a0c4204cd8be95cd5e969a0679136a3d54b6fc97f754c745fb9b072d2629
- TakerPaymentSpent: e5c5bd5fbc0ac91133001ef408e8340ea46dbe8e92c629ef169a0c1b804ee27c
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.