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.
e390a75d38baeb4fe61345e7bbe071cfda560d10db6ebc068fbb782dcbd86a58
no server returned transaction e390a75d38ba…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent: e390a75d38baeb4fe61345e7bbe071cfda560d10db6ebc068fbb782dcbd86a58
51f3c9895794eb34d0ae0da148985f5fa9e5e6684517f511b8e8240b562d5680
confirmed on-chain, locked to this swap's secret hash
- TakerFeeValidated: 31dc83ed35e471198c1804593b0f0b022cac32842c49746173be847c895c148b
- TakerPaymentReceived: 51f3c9895794eb34d0ae0da148985f5fa9e5e6684517f511b8e8240b562d5680
- TakerPaymentSpent: 2595e3cf67682d5ce040206ff44766a5eb25c1bcd80966b660e7592d631e0853
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.