Skip to content

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.

Totals

Validators

287,841

31.52% of the 913,300 indexed

Active

287,841

none exited

Effective stake

9.21M ETH

sum of effective balances

Slashed

0

no compounding credentials

Validators

287,841 in this group

287,801–287,841 of 287,841 validators

Validators withdrawing to 0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f
ValidatorStatusEffective balance
#2,356,3650x97393d68…78e09ca1active32.00 ETH
#2,356,3660xb3be5561…d9b02458active32.00 ETH
#2,356,3670xb9edb77d…c33cab59active32.00 ETH
#2,356,3680x967d2977…d6522392active32.00 ETH
#2,356,3690x89bd4cdb…b54b1c6aactive32.00 ETH
#2,356,3700x8f3ad178…5f8c93aeactive32.00 ETH
#2,356,3710xb84b8897…ef57b17eactive32.00 ETH
#2,356,3720xb3bc43ff…98ef8b7dactive32.00 ETH
#2,356,3730x8c94ccee…a4a63e6dactive32.00 ETH
#2,356,3740xa54a841c…4d183978active32.00 ETH
#2,356,3750xab224dc9…02c49d49active32.00 ETH
#2,356,3760x8324ecde…cf73cefdactive32.00 ETH
#2,356,3770x87f1f722…f841bf84active32.00 ETH
#2,356,3780xa66cd3dc…8d26f5b8active32.00 ETH
#2,356,3790xb2694418…4a1b2a84active32.00 ETH
#2,356,3800xb208f6a5…bf21ef31active32.00 ETH
#2,356,3810x8ae842f0…54866e46active32.00 ETH
#2,356,3820x8cd30421…f2df2d7bactive32.00 ETH
#2,356,3830x94353cb3…9b45308bactive32.00 ETH
#2,356,3840x8e211e3e…f8672917active32.00 ETH
#2,356,3850xb3a41c51…5e60afaeactive32.00 ETH
#2,356,3860x8aceb982…7c4c168cactive32.00 ETH
#2,356,3870x89af3e9b…a2d15810active32.00 ETH
#2,356,3880xb0ddc89f…fe0ed32eactive32.00 ETH
#2,356,3890x991a20a3…bb0fb41bactive32.00 ETH
#2,356,3900x970ec462…19ba42edactive32.00 ETH
#2,356,3910xb679d2aa…c3fced5factive32.00 ETH
#2,356,3920x8f0eb532…c9dc3eb7active32.00 ETH
#2,356,3930xabe0c10b…7b8d41d3active32.00 ETH
#2,356,3940x8bd58a6f…709d0306active32.00 ETH
#2,356,3950xb035cbe6…d1f0f532active32.00 ETH
#2,356,3960xaa2603c2…0b941a63active32.00 ETH
#2,356,3970xaa8f4f3b…4d5ee5ebactive32.00 ETH
#2,356,3980xb0bc742b…8031e647active32.00 ETH
#2,356,3990xaa061bb1…7d617d81active32.00 ETH
#2,356,4000xaa4048b9…07dece1bactive32.00 ETH
#2,356,4010xa93830ed…9e390f78active32.00 ETH
#2,356,4020xa58f6be1…af825535active32.00 ETH
#2,356,4030x81045d26…50cf3513active32.00 ETH
#2,356,4040xa312f669…7aee84b2active32.00 ETH
#2,356,4050xb9e9b5a3…d4e49d3bactive32.00 ETH

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