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

298,490

32.03% of the 931,834 indexed

Active

298,490

none exited

Effective stake

10.26M ETH

sum of effective balances

Slashed

4,520 compounding (0x02)

Validators

298,490 in this group

Validators withdrawing to 0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f
Validator	Status	Effective balance	Balance	Credential	Activated
#2,374,7900xb7002d44…4e89644b	active	32.00 ETH	32.00 ETH	0x01	epoch 478,596
#2,374,7910x8322bfcd…a9b95c21	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7920xb14d713a…29f7e39c	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7930xab48c9b9…f4dd95fa	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7940x8d0cb9fd…219933a3	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7950x9363dbb2…bc1aa7c4	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7960xb44b73a4…b87cabe8	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7970xaf0ca9c6…2de9218c	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7980x93a5c6ab…1f97293c	active	32.00 ETH	32.00 ETH	0x01	epoch 478,597
#2,374,7990x96e0a87d…c333933f	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8000x80a80cd8…a5b6e5a9	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8010x97f86a7c…9ecc2bf3	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8020x97a5a17a…4d832ade	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8030x894982bb…7b2cc310	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8040x94a79770…4aa9ef0b	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8050x9956c1af…ff98df10	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8060xb7b4ad0c…de3745ed	active	32.00 ETH	32.00 ETH	0x01	epoch 478,598
#2,374,8070x956bb645…3dcb2485	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8080x88ebd947…014e0766	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8090x891025ea…ed19d751	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8100xac0d0f00…4d54116e	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8110x988a650f…c6811986	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8120xa5692886…fa2d46d1	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8130xb1d3e57a…ba6a10c1	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8140x91b6d47f…cd62b29e	active	32.00 ETH	32.00 ETH	0x01	epoch 478,599
#2,374,8150x84815677…22e6731a	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8160x8ecf26a2…872ca5c5	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8170xa0c20a1a…c940de8f	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8180x83232b33…04c80881	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8190x830b1168…7ad55de4	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8200xb90d644d…e5b3c272	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8210x911b5b79…80980e76	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8220x83041d09…dc1cd0b2	active	32.00 ETH	32.00 ETH	0x01	epoch 478,600
#2,374,8230xa4923c64…d1d82134	active	32.00 ETH	32.00 ETH	0x01	epoch 478,601
#2,374,8240xb5aea2f4…cb3b694c	active	32.00 ETH	32.00 ETH	0x01	epoch 478,601
#2,374,8250x87910ebf…f77e1946	active	32.00 ETH	32.00 ETH	0x01	epoch 478,601
#2,374,8260x9998c29e…c1ad0a58	active	32.00 ETH	32.00 ETH	0x01	epoch 478,601
#2,374,8270xacb361d6…409dccda	active	32.00 ETH	32.00 ETH	0x01	epoch 478,601
#2,374,8280xb0d7a187…449dccd9	active	32.00 ETH	32.00 ETH	0x01	epoch 478,601
#2,374,8290xa1ef3f2e…a1cc3d0a	active	32.00 ETH	32.00 ETH	0x01	epoch 478,601

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