ETH Price: $2,509.03 (+0.41%)

Block

#0x44f900c5c0d1be7f2fe68ab7870d04541ec58799c08d69221cf15b1493b76e0f
Block Height:
18473846
Status:
Finalized
Timestamp:
362 days ago (Nov-01-2023 01:01:35 AM +UTC)
Proposed On:
Block proposed on slot 7664706, epoch 239522
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.065318738269174628 ETH (0 + 0.509851511567789888 - 0.44453277329861526)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
59,538 bytes

Gas Used:
16,168,215 (53.89%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000027494239364 ETH (27.494239364 Gwei)
Burnt Fees:
šŸ”„ 0.44453277329861526 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,847.63 / ETH
Hash:
0x44f900c5c0d1be7f2fe68ab7870d04541ec58799c08d69221cf15b1493b76e0f
StateRoot:
0x5dbbe9bbecd06db6c37c74075bb16f5252bd04cc960ab4c6415ab37c64caf68f
WithdrawalsRoot:
0xfa94ba954ee98024105319b114f7d1a369d028217039a595b3eef056f730067d
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0xbf46a9b52be8077af62bc837320fae20e33a8b61768f07adb248753afd7eed20
Parent Root Hash:
0xe5fd44cec06c84d652c3872a3cec1131951f9752f970473a03ea862707f1cdea
Beacon Chain Deposit Count:
1030089
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x30856fdab1573d173df2a88d1ed8d78b4775a57925f8e11ed7f296afbdd02289
Randao Reveal:
0x86ffddd737a7827eaab033743ba250f7ed3f5b72a1a54a22671914506d778945c2fc23a69682d09c4c4ab36fb613349c09ec2f8eef80476fcfc82de91e28ff240bc88ba643214fbc2e6ee9244b92a333f4c3911c6bdef424cbefb79a1b9363da
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.064810813142597224 ETH
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:

Blocks are batches of transactions linked via cryptographic hashes. Any tampering of a block would invalidate all following blocks as all subsequent hashes would change. Learn more about this page in our Knowledge Base.