ETH Price: $3,356.93 (-2.29%)

Block

#0x308a9c53982c2668c384943110fb513b56462fee22d1adb2727e27cd1dfd4f4d
Block Height:
20684572
Status:
Finalized
Timestamp:
82 days ago (Sep-05-2024 01:05:47 PM +UTC)
Proposed On:
Block proposed on slot 9893127, epoch 309160
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.023476081792074941 ETH (0 + 0.063189438679265753 - 0.039713356887190812)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
64,642 bytes

Gas Used:
13,981,842 (46.61%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002840352286 ETH (2.840352286 Gwei)
Burnt Fees:
šŸ”„ 0.039713356887190812 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,367.89 / ETH
Hash:
0x308a9c53982c2668c384943110fb513b56462fee22d1adb2727e27cd1dfd4f4d
StateRoot:
0x7f34dfc66ea0619c9fe4b89ba07f7e6b8901da174218aab162be7e8250392450
WithdrawalsRoot:
0xad7a0f4cca071bbb8cde624f37b2e199a1629baa0c58b482578d0f95f57f3838
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0x20a94556decb3c7b6a20b8790d455cddcd69fbc64eabe2451d0fe33f6d50e3a8
Parent Root Hash:
0xf1fbab2a4ca34a3f8cb2d82bd04b7f673a9d5acab1114fd17681c88b6da42448
Beacon Chain Deposit Count:
1671859
Slot Graffiti:
Tim Beiko is a cool dude (Hex:0x54696d204265696b6f206973206120636f6f6c20647564650000000000000000)
Block Randomness:
0x2464e7fa68e2d41dd603e37235ae64a90677994f966d0abd67c488370816b7b2
Randao Reveal:
0x867477daab1ec4b201618f490361232ebdb384eb0d3a2d8b97ddbacc9ead22d5a0195fa6e8332d6aacf5699e00eee62719e8bb1706d2ccbe7a231b5ba6007a5b3521e09ba3f942033ca22e97481dba58d2c41aa4fb21be61713d5e7d80f857a4
MEV Reward:
0.023709087589328072 ETH
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2.00 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432

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.