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.
9663f46e8f0f6ea7eb7671bc155ee1b7cf593f5e0085b5cb46d795eeb2806b29
no server returned transaction 9663f46e8f0f…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent: 9663f46e8f0f6ea7eb7671bc155ee1b7cf593f5e0085b5cb46d795eeb2806b29
bc4170a1634a9d8d2dc64a4db7b38f74d0ce54e730062fa528b6cacc739e3b32
confirmed on-chain, locked to this swap's secret hash
- TakerFeeValidated: ff02ff0d7c8bb08c62f303baace39feccb65db62c319867d1649843f01c262c1
- TakerPaymentReceived: bc4170a1634a9d8d2dc64a4db7b38f74d0ce54e730062fa528b6cacc739e3b32
- TakerPaymentSpent: 495700b9d98cd2011f28806269610f5db80038a30276b0a558949b848d2eeb96
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 defistats-gleec.