Anyone staking ether today waits first. On 17 August 2026, 2,229,411 ETH sat in Ethereum's deposit queue, spread across 37,498 individual deposits. Those deposits do not get their turn immediately, because the protocol activates only a firmly capped amount per unit of time. That works out at roughly 39 days in which your capital is tied up and not yet producing any reward.
In the opposite direction almost nothing was happening at the same moment. The exit queue held exactly two validators with 64 ETH between them. The way in is currently long, then, the way out practically clear. cryptoticker.io carried out this survey itself on 17 August 2026.
Staking on Ethereum means that ether is lodged as collateral and the associated validator takes part in running the network in return. The deposit alone is not enough for that. Between the moment the balance reaches the deposit contract and the moment the validator actually takes part and receives rewards, there is a queue.
This queue is not a provider's administrative step but a rule of the protocol. Ethereum deliberately limits how quickly the set of active validators may change. The reason lies in the network's security: if very many participants could enter or leave at the same time, the composition of the validator set could be shifted substantially in a short space of time. The limit makes such jumps impossible and spreads every change across days or weeks.
For you as an investor that has a very concrete consequence. Time in the queue is dead time. The balance has already left your own account but is not yet working. Anyone with an annual reward in mind who plans an entry point around it is calculating too optimistically without this lead time. How differently providers handle this phase can be read in our overview of staking platforms compared.
The basis is our own queries made directly against the chain, not figures taken over from a report. The basis is a public beacon node providing the standard interface of the Ethereum consensus layer. We queried the state of the network at slot 15,012,295, which corresponds to epoch 469,134 and to 17 August 2026 at 12:59:23 UTC.
The method in one sentence: we queried the pending deposits, the exiting validators, the pending partial withdrawals and all validator balances, formed the active validator set from the committee assignments of the same epoch, and intersected the balances against that set. In doing so we checked 2,336,544 validator balances, 898,493 active validators, 37,498 pending deposits and 35 pending partial withdrawals. Every query returned HTTP 200.
The number of deposits is not the same as the number of new validators, and that matters for interpretation. 34,652 entries are for exactly 32 ETH, the minimum amount for a standalone validator. Behind those sit new validators with high probability. Alongside them are 216 entries above 31 ETH, 80 above 1,024 ETH, 73 above 1,800 ETH, 62 above 1,900 ETH and 59 above 1,920 ETH. Amounts of this order have been possible since the Pectra upgrade, because a single validator may hold up to 2,048 ETH. Such amounts are as a rule top-ups of existing validators or consolidations, not new entrants. At the lower end there are 58 entries above 1 ETH and 56 above 0.005 ETH.
For the waiting time, however, this distinction plays no part. The protocol measures the queue in ether and not in heads. Whether 2.23 million ETH is made up of 70,000 small or 3,000 large deposits changes nothing about the duration.
The bottleneck has a name and an exact value. The protocol limits the amount of balance that may be newly activated per epoch. We queried the applicable value through the same node's configuration interface rather than setting it from memory: the upper limit is 256 ETH per epoch. An epoch comprises 32 slots of twelve seconds each, so it lasts 6.4 minutes. That gives 225 epochs in a day.
This upper limit is a cap and not the base figure. In principle throughput follows the size of the network and amounts to one 65,536th of the total active balance. At the 42,240,256 ETH we measured, that would give 644.54 ETH per epoch. Because the cap applies, 256 ETH of that remain. The network has therefore grown well past the point at which the fixed upper limit binds. The limit becomes relatively tighter with every further increase, without changing in absolute terms. The technical derivation of this limit is set out in the protocol's associated improvement proposal, which is publicly available: EIP-7251.
The waiting time follows from these two figures without further assumptions. 256 ETH per epoch times 225 epochs gives 57,600 ETH that can be newly activated each day. Divide the measured 2,229,411 ETH by that daily throughput and 38.7 days stand on paper.
This figure describes the state at a single moment and is not a forecast. The value holds exactly if not one further deposit arrives from the moment of measurement. That is precisely what does not happen. As long as new deposits keep coming in daily, the end of the queue shifts further back, and anyone joining today waits longer than the calculated value. If, conversely, hardly anything more arrives, the backlog clears faster. The 38.7 days are therefore to be read as an order of magnitude and not as a date.
More remarkable than the crush at the entrance is the finding on the other side. At the time of measurement exactly two validators were exiting, 64 ETH between them. Measured against 42.24 million ETH of active balance, that is a share which can no longer meaningfully be expressed as a percentage.
In practice that means: anyone ending a validator today stands in no queue worth mentioning. The protocol's fixed lock-up period remains, which is covered further below, but no backlog caused by other leavers. For liquidity planning this is the more important of the two figures. The exit queue has repeatedly been the point in the past at which staking turned unpleasant, because the way out dragged on for weeks. That situation does not currently apply.
What the finding does not say: it says nothing about the intentions of the remaining participants and permits no conclusion about how long this state will last. An empty exit queue can fill within a few days if many participants want to leave at once. The finding is a snapshot of the present and not an assurance about the future.
To place the two queues, you need the quantity they relate to. At the time of measurement, 898,493 validators were active. Their total balance stood at 42,240,256 ETH. That gives an average balance of 47.01 ETH per active validator.
This average lies noticeably above the minimum of 32 ETH, and that is a consequence of the rule change already mentioned. Since validators have been allowed to hold more than 32 ETH, larger operators have been consolidating their positions instead of starting a separate validator for every further stake. The number of validators therefore grows more slowly than the balance staked, and the validator count loses explanatory power as a metric. Anyone wanting to follow the development of staking should look at the balance.
The 2.23 million ETH in the entry queue correspond to 5.3 percent of the active balance. That is the growth already deposited and merely waiting to be let through. Were the queue worked off completely without anyone exiting, the staked balance would grow by exactly that share.
The comparison with throughput shows how tightly capacity is set. 57,600 ETH a day, against 42.24 million ETH of active stock, is a share of roughly 0.14 percent. So at best the protocol lets its stock grow by about one seven-hundredth per day. That figure explains why a backlog does not clear quickly once it has formed. The same figure explains why the network stays stable in turbulent phases.
The waiting time can be translated into a quantity more relevant to the investment decision than the days themselves. A validator that spends 38.7 days in the queue is active for only 326.3 of the 365 days in the first year after its deposit. In that first year it therefore receives, on the arithmetic, 89.4 percent of what an already continuously active validator receives over the same period.
Put differently, the first year's reward melts away by 10.6 percent through queuing alone. This calculation rests solely on the waiting time we measured ourselves and on the number of days in the year. No assumption about the level of the reward enters into it, because that depends on factors which change daily and which we did not survey. The effect is purely temporal in nature and hits every level of reward in the same proportion.
From the second year the discount disappears, because the validator then runs continuously. Anyone planning for the long term should therefore not overrate the effect. Anyone reckoning with a one-year horizon, by contrast, loses a double-digit percentage share of the expected reward to a queue that appears in no yield figure.
The waiting time we measured applies to the route via a new or topped-up validator. Not every route into staking runs that way, and that is the most important qualification in this article.
Anyone buying a liquid staking provider's share token on the market acquires a claim on staking that is already running. In that case no new validator is created, and no queue is passed through. The price for it is a different risk position, because a set of contractual terms and a market price stand between you and the protocol. Something similar applies to exchange-traded products that pass on staking income: there too a counterparty stands at the end between you and the validator.
With staking offerings from trading venues the position is mixed, and we cannot resolve it with the data collected. A provider with sufficient stock of its own can serve a customer immediately and carry the queue itself. Another passes the waiting time on unchanged. This cannot be read off the chain, because only the validator is visible there and not the contractual relationship behind it. If you want to know what applies in your case, you will find the answer solely in your provider's terms. Which providers have to be licensed in Germany for this at all is set out in our piece on staking under MiCA.
For tax the waiting time is undramatic, and that is good news. Staking rewards are regularly treated in Germany as income from other services under section 22 no. 3 of the Income Tax Act, and what governs is the moment of inflow. Anyone standing in the queue receives nothing, and without an inflow no taxable event arises.
Under this scheme the deposit itself likewise does not trigger a sale, because no asset is exchanged for another. The ether stays ether and merely changes its purpose. That is the difference from a swap into another token, which would count as a disposal.
The practical work begins with the first reward, and it begins immediately. From that point every single inflow counts, with its date and euro value. The waiting time is therefore a good moment to prepare the record-keeping rather than reconstructing it later from block data. For individual questions about your personal position, tax advice is the right route, because we are not tax advisers.
Besides a full exit there is the partial withdrawal, in which a validator stays active and only draws off balance above its stake. These operations too stand in a queue. At the time of measurement, 35 partial withdrawals totalling 86.28 ETH were pending. That is a quiet figure, consistent with the picture of an empty exit queue.
Anyone exiting fully then has to wait out a fixed lock-up period before the balance can be withdrawn. The period is 256 epochs, which at 6.4 minutes per epoch amounts to a good 27 hours. We queried this value through the node's configuration interface as well. It applies regardless of how full the exit queue is and cannot be shortened. Only once this period has elapsed does the balance travel to the withdrawal address on file.
The survey rests on a single measurement at a single point in time. A number of limitations follow from that, which we disclose because they bound what it can show.
We did not collect a time series. Whether the entry queue is currently growing or shrinking cannot be derived from a single snapshot, and so we do not claim it either. We do not know the level of the reward, because we did not survey it. We do not know who the waiting deposits belong to, and therefore cannot say what share falls to private investors, to providers or to institutional entrants. We cannot resolve how individual providers pass the waiting time on to their customers, because that relationship lies off the chain. And we queried only a single node, albeit through the standardised interface.
What is certain is what was measured directly: the amount in both queues, the number and size of the deposits, the number of active validators, their balance and the applicable protocol limits. All values derived from these, in particular the 38.7 days and the 89.4 percent, are calculations on that basis and not measurements.
(As of August 17, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)
