> For the complete documentation index, see [llms.txt](https://docs.husher.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.husher.io/documentation/how-husher-works/how-it-works/confirmations-and-execution-timing.md).

# Confirmations and Execution Timing

Per-network confirmation thresholds and the typical end-to-end execution time once confirmations are reached

Once funds are sent, Husher monitors the deposit in real time. Execution begins as soon as the required number of network confirmations is reached. The confirmation threshold varies by network and reflects the finality guarantees of each chain.

### Confirmation thresholds

| Network  | Confirmations required |
| -------- | ---------------------- |
| Ethereum | 4                      |
| Base     | 24                     |
| Solana   | 24                     |

### Execution timing

Under normal conditions, most standard swaps complete approximately **30 seconds** end-to-end after confirmations are reached. This timing reflects execution against centralized-exchange spot liquidity, not on-chain settlement delays.

{% hint style="info" %}
The 30-second figure applies to Float and Fixed orders. Private Mode orders take longer due to the additional routing steps through privacy-focused networks. Typical Private Mode processing time is around 5 minutes or more.
{% endhint %}

The confirmation wait itself depends on block time and network congestion for the input asset's network. Husher begins execution immediately once the required confirmation count is met and no additional delay is introduced.