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.
6cdb0d138d4e14d30c770861ce63e299f3761f1d426b8140f0afad958f55ab43
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 6cdb0d138d4e14d30c770861ce63e299f3761f1d426b8140f0afad958f55ab43
- MakerPaymentSpent: bdb3b095255a6f50c49514722df97c4293de451e855ae5b23d2c30bd29d76c49
ae132286e0284ce9b81d3106e45a6f4ff3aa524be970337c3a41dc2388e08940
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeValidated · TakerFeeSent: 65284213ad7f3d20bc4bbdd155b65235d618893219d40caeed86d5b4dba0074e
- TakerPaymentReceived · TakerPaymentSent: ae132286e0284ce9b81d3106e45a6f4ff3aa524be970337c3a41dc2388e08940
- TakerPaymentSpent: 7a916b88c97471a72e7cba22faaacab1576834217a8c0ff043e08a70f3c1da91
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.