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.
05ffc2b6dc64d927c76d7a981bec68bfc17348fa4f627805e6abdaffb60bcff5
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 05ffc2b6dc64d927c76d7a981bec68bfc17348fa4f627805e6abdaffb60bcff5
- MakerPaymentSpent: d68923bc954d7ad4ce839a78f9543b64471491194447150db9dfe687439261c9
7fb5e917d3c6d1f4480f76ac588dca70a20f8256f4cb784454be0dea4028d4a1
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 8df608c417ba705c736422f0fd2c6bd1579792f1d9a51286d2a6e21393305448
- TakerPaymentSent · TakerPaymentReceived: 7fb5e917d3c6d1f4480f76ac588dca70a20f8256f4cb784454be0dea4028d4a1
- TakerPaymentSpent: a902594a2921db2903202243f8173b4318c2868f77c1b48f7685d55d22b26d39
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.