ETH Price: $2,717.54 (-1.73%)

Block

#0xb17a78548fd5f5b5d6ff8b14597f0c6c97ab2d5b69d814eb8f4d4017c490ca25
Block Height:
17070625
Status:
Finalized
Timestamp:
496 days ago (Apr-18-2023 02:27:59 AM +UTC)
Proposed On:
Block proposed on slot 6246738, epoch 195210
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.318716924024811682 ETH (0 + 1.163521453928389922 - 0.84480452990357824)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
91,964 bytes

Gas Used:
22,398,760 (74.66%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000037716575824 ETH (37.716575824 Gwei)
Burnt Fees:
šŸ”„ 0.84480452990357824 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$2,104.28 / ETH
Hash:
0xb17a78548fd5f5b5d6ff8b14597f0c6c97ab2d5b69d814eb8f4d4017c490ca25
StateRoot:
0xde74fe40a2e3f03bdada94e61d77fb6e3d110cfcd012030e2bc72408e5920fec
WithdrawalsRoot:
0x5d337efe15588a512b078edfe2eed85b79a27959cbf3718904b3a550647c1b36
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0x9b15600fe33bad7b55f1c4a153bff7d3269b4e51a1685ec70f03c0334f0ee6cb
Parent Root Hash:
0x83523f0b3db918a55034cdb07f353995180c259f5cd05e7392f4fc72c0fbcb1e
Beacon Chain Deposit Count:
595920
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x5992cf2df7cd1003991683beb91eef7511a3e90c77c56c12c0e641076a804e06
Randao Reveal:
0x9037211cb359bd664f4fcc90ea666450e41986c7acfa4a739e4669359da1123e891bb2318098e6d59c95c8a3e47021040197edebc53e988ea0e17fdb7f66b98fd3db8119df4d406f85c868dbd21e08cac9eb89872ef6cda0edef34d1d753d698
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.473082972816767218 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.