Requested stETH awaiting finalization
Home
Lido Withdrawal WatchExit queues · liquidity · finalizations
Loading data…Reading withdrawals…
WITHDRAWALS / MAINNET
From exit to claim.
Follow withdrawal demand, expected ETH arrivals and completed finalizations.
Submitted requests not yet finalized
Finalized ETH not yet claimed by request owners
ETH made claimable over seven calendar days
Ethereum validator exit queue
Ethereum Mainnet · network-wide scheduled exits · Lido and other validators
Reading the network’s Beacon exit schedule
Balances and exit epochs are checked against the selected network.
Source: Beacon API · Ethereum Mainnet. This is separate from Lido’s stETH withdrawal queue.Withdrawal funding balance
Demand + deposit lock versus current ETH + expected incoming
Required ETH— ETH
- Withdrawal demandUnfinalized stETH · 1:1 ETH planning value
- — ETH
- Deposit lockCurrent reserve + estimated future deposit consumption
- — ETH
Current + expected ETH— ETH
- Current bufferETH already held by Lido
- — ETH
- Already in vaultsWithdrawal Vault + EL Rewards Vault
- — ETH
- Incoming from exitsScheduled exits expected within this period · excludes consolidations
- — ETH
- Incoming EL rewardsProjected from recent rewards-vault arrivals
- — ETH
- Incoming CL rewardsProjected from matched accounting reports
- — ETH
Calculating the funding balance…—
Reading Lido reserves, scheduled exits and recent reward reports.
What is included
This is a planning estimate using the same ordinary-exit withdrawal horizon as the queue widget. Demand is the current unfinalized stETH amount at a 1:1 ETH planning value; future requests and new user deposits are excluded. The right side includes current buffer and vault balances once, then adds forecast future inflows.
Deposit lock includes the current effective deposits reserve plus an average future allowance: half of min(deposits reserve target, maximum withdrawal request) for each complete accounting frame in the horizon. Using the full buffer on the right requires including its protected deposit reserve on the left.
Exit balances come from Lido keys verified through KAPI, exclude consolidation sources, and are capped at 32 ETH for 0x01 or 2,048 ETH for 0x02 validators. Only exits whose withdrawable time plus the average sweep wait falls within the period are included. Known excess above those caps is included with CL rewards rather than counted again as exit balance.
Future EL rewards use recent vault-arrival averages. Future CL rewards use matched ETHDistributed and TokenRebased accounting reports: post-CL balance + withdrawn ETH − pre-CL balance, divided by report time. Returned stake therefore does not become projected rewards. CL reward accrual can compound instead of arriving as cash within the period; the forecast is not a guarantee of immediately available ETH.
Live queue and funding estimates above load independently. Missing data is not shown as zero.
How a Lido withdrawal progresses
A validator exit and a stETH withdrawal request are different queues.
- 1 · Requested
The request enters Lido’s FIFO queue. Available buffer and vault ETH can help fulfill it without a new validator exit.
- 2 · Finalized
An oracle report locks the corresponding ETH. Finalization depends on available liquidity, accounting and safety checks.
- 3 · Claimed
Once finalized, the request owner claims the ETH. “Ready to claim” is already reserved and is excluded from the funding forecast.