Ethereum withdrawal address

Lido · liquid staking protocol

0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f

The Lido Withdrawal Vault. Every validator in the Lido protocol withdraws here, across all of its node operators — so this identifies the protocol, not which operator runs any individual validator.

Verified against the operator’s own documentation.

Validators

284,491

31.30% of the 909,019 indexed

Active

284,491

none exited

Effective stake

9.10M ETH

sum of effective balances

Slashed

no compounding credentials

Validators

284,491 in this group

Validators withdrawing to 0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f
Validator	Status	Effective balance	Balance	Credential	Activated
#2,352,1570xb9a0d8e8…434b593c	active	32.00 ETH	32.00 ETH	0x01	epoch 472,441
#2,352,1580xb704eeb9…04b83f63	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1590xae626df4…1c7a0cd3	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1600x8414a552…62044e7a	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1610x9678c7f7…d1eb0895	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1620x860a7de9…57093dd9	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1630x84445429…5b0fa13d	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1640x896876b6…3add7c94	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1650x8f8ed581…7b758531	active	32.00 ETH	32.00 ETH	0x01	epoch 472,442
#2,352,1660x80327a17…fa8b65f4	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1670xb1b8808c…af3b7c62	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1680xb6a609ec…46ffafbc	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1690x82fe5952…1237bddf	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1700xaa371564…3607834b	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1710x85f4a5ed…3ee5899e	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1720xb4d93a74…74afbe4f	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1730x921d6383…8536f159	active	32.00 ETH	32.00 ETH	0x01	epoch 472,443
#2,352,1740xa981d9f0…67f9c03e	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1750x8d6edc7a…f29693fa	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1760xac366b05…a7d88d32	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1770xb5b7c9f8…d7d49700	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1780x92c55d53…d32423d4	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1790xb15b21db…cdeba6b6	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1800xb60077f1…2f02b46b	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1810xa1685d44…8ba3a10d	active	32.00 ETH	32.00 ETH	0x01	epoch 472,444
#2,352,1820x96e3d916…ea7e2e55	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1830x93a7fc94…556c37dc	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1840x988757b5…37c35be0	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1850xac7536c3…accec568	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1860xa3256f7c…c8017396	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1870xb415a860…4a1717b7	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1880x83968eb2…5c0f96d0	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1890xa0438f87…78c0e780	active	32.00 ETH	32.00 ETH	0x01	epoch 472,445
#2,352,1900x8f2ea07e…10197fd5	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446
#2,352,1910x9561f657…db066bdb	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446
#2,352,1920x919bb96d…bb438cbb	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446
#2,352,1930xa95435c5…e66cb8c0	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446
#2,352,1940xa2aa913a…2f179f74	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446
#2,352,1950x92b3279d…78fb05f4	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446
#2,352,1960xb98cd02b…6b2eaf35	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446
#2,352,1970xab9a21ad…f26e51b3	active	32.00 ETH	32.00 ETH	0x01	epoch 472,446

How this address was derived

An Ethereum validator’s withdrawal credentials are 32 bytes: a one-byte prefix, eleven zero bytes, then a twenty-byte execution address. Prefix 0x01 and 0x02 carry one; 0x00 is a BLS key with no execution address in it at all, and reading its last twenty bytes would produce an address that looks real and belongs to nobody.

The operator is named only where the address is a publicly documented protocol contract, with a link to the documentation. An explorer’s label is not enough: those are crowd-sourced, and attaching one here would publish a claim about who controls a large share of the stake on the basis of a wiki edit.

Full methodology

Totals

Validators

Active

Effective stake

Slashed

Validators

How this address was derived