Block
#20064129
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
622 days ago (Jun-10-2024 09:30:59 PM +UTC)
Transactions:
199 transactions and 55 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.05206071997633873 ETH (0 + 0.23422604516615193 - 0.1821653251898132)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
71,010 bytes
Gas Used:
15,096,880 (50.32%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012066422015 ETH (12.066422015 Gwei)
Burnt Fees:
š„ 0.1821653251898132 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,665.99 / ETH
Hash:
0x33fe5a80f1c51e81d81bf7d4117be255915f79f1c8b0df9aa698b2d3c1ae74c8
StateRoot:
0x835059fee4f628beb8e88548393ad515bebde196da440ff69a35f7ec3aa0e799
WithdrawalsRoot:
0xb274792808d58b22eee0978893290415dee88a79b996a3af53d7faa405dbe13a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x7e55c9929c6489c572d90ff142eadda66f3cd9a8adeb7600b771b0487616f0cc
Parent Root Hash:
0x8193cfa255bf05fa40b3a354bfde29a9352bb6330bbe52d0ea3e387e6f5e2641
Beacon Chain Deposit Count:
1527996
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x49890da2048ee6cbfe1c5cf6e071f2b66e2419e120e41c88fc41b96fe03d7a37
Randao Reveal:
0xad5c925d95c8e3cc2c9f5631ee8f9a4a288d79c4747ca0410519f2ce0ee3edf93430f72cae06c7e3b5a92ddcc8f70ab4039e55ca34b86362bc6ceae7d03b0acacbddb5a37d3e1a06757b415c6e1217df1090e822f55ae4f2ee23a73061f5e2b3
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.047054875483415924 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000131072 ETH
Excess Blob Gas:
0 (0 blobs)
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.