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.
5dde7e56fcfde620a9839ad3b5be622609635e1dc328087d97c97b840bf7a473
no server returned transaction 5dde7e56fcfd…: either the chain does not have it, or its servers cannot look up a transaction by id
- MakerPaymentSent · MakerPaymentReceived: 5dde7e56fcfde620a9839ad3b5be622609635e1dc328087d97c97b840bf7a473
- MakerPaymentSpent: ac4853c4e6cfcc7cf3199d25f762ae178b5de4f133ae02d3a6a7791ecc6e76dd
9c3e93e2fbee15664f882f247ce92d3b0aa927f6ae4cdbd2ff818f06f04759a8
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 67e13edc4f2f97f9e705d382d430275f41dfdd1a823d356f3fa1cde62e14a69e
- TakerPaymentReceived · TakerPaymentSent: 9c3e93e2fbee15664f882f247ce92d3b0aa927f6ae4cdbd2ff818f06f04759a8
- TakerPaymentSpent: b85e5b1de15743fcff984ff24ff549d8961dac3ce6d0eb872ebae4a10062d708
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.