Skip to content

Ethereum withdrawal address

0xf63b7fb090d10238d791a69c3614e7f9baed004a

No operator is published for this withdrawal address. Ethereum validators carry no name on the beacon chain, and a label taken from a crowd-sourced explorer would be a guess about who controls stake.

Totals

Validators

4

0.00% of the 965,670 indexed

Active

4

none exited

Effective stake

128.00 ETH

sum of effective balances

Slashed

0

no compounding credentials

Validators

4 in this group

4 validators

Validators withdrawing to 0xf63b7fb090d10238d791a69c3614e7f9baed004a
ValidatorStatusEffective balance
#1,491,5690xa924067d…0dd30583active32.00 ETH
#1,491,5700xafda43fc…75a7e852active32.00 ETH
#1,491,5710xb9f68c55…4898068eactive32.00 ETH
#1,493,7860xb1db894f…dcb8dba0active32.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
Ethereum withdrawal address 0xf63b7fb0…baed004a · RPCNode.IO