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.
aabf7a9c72047061dfb516a5f3cd64f829ce901571b261bf5b502a861300c486
no server returned transaction aabf7a9c7204…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent · MakerPaymentReceived: aabf7a9c72047061dfb516a5f3cd64f829ce901571b261bf5b502a861300c486
- MakerPaymentSpent: fdc7254150d7c6ca3673cba65932ec319a52ba52a2b109bf3943d0e8dc1bba2f
5ca703112448191411dd283ce3a605f28ffa218af934dc5a93dfa9b49ce1f5fe
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 949aec82610eef53c216b7ba01f072a5db340eae48329738d2d86aa893f1d1f3
- TakerPaymentSent · TakerPaymentReceived: 5ca703112448191411dd283ce3a605f28ffa218af934dc5a93dfa9b49ce1f5fe
- TakerPaymentSpent: e88b1de33f007ac174fb70b28fe147b022c210eb1981edebf5b16ccaccca4b41
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.