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.
676af9c64cb5fdb47c0c4ae090dd210d224695a230d0ffaf28adedb3a36dda1d
no server returned transaction 676af9c64cb5…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent · MakerPaymentReceived: 676af9c64cb5fdb47c0c4ae090dd210d224695a230d0ffaf28adedb3a36dda1d
- MakerPaymentSpent: 8b5e8998c8269377d5061006f7340cad8fcd3e18656ccb7ddcd2d09ed3ec8e52
4ce91ae3ff18c7d458e0a30c492c414030fb146c8b4274dd31c217c2ddea592f
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: c6227e51d1ff1de446f9ccb245c2eae7f8986272a1bc185a7df60fb59e2d2aaf
- TakerPaymentSent · TakerPaymentReceived: 4ce91ae3ff18c7d458e0a30c492c414030fb146c8b4274dd31c217c2ddea592f
- TakerPaymentSpent: 1c774fb0b816d8e56e51be24d5de0f9cea9d818d6992e9f95f3e46cf59cdf5e1
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.