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.
789eb5a76897df110be7ff3c2fb9657407ff34cfe374c28c35d491f53813d8d0
no server returned transaction 789eb5a76897…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent · MakerPaymentReceived: 789eb5a76897df110be7ff3c2fb9657407ff34cfe374c28c35d491f53813d8d0
- MakerPaymentSpent: ca6f3f5eeb8c18a204feea78be587c37ade0c318ca597ee95029595f4e19c442
4038b479280f236aaaf423761385462cbbee24d0855f71b7461a4f4b8d42294a
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 28ab36c4aae755dd5950f5e46d0747a15a000e414af9a7baf872542a64a3b259
- TakerPaymentSent · TakerPaymentReceived: 4038b479280f236aaaf423761385462cbbee24d0855f71b7461a4f4b8d42294a
- TakerPaymentSpent: bc3020c06fc765a46f5ada1a52cf095017fe1a04e08554148d1979f41094ee80
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.