Block
#20097984
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
629 days ago (Jun-15-2024 03:07:47 PM +UTC)
Transactions:
257 transactions and 128 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.0520985921934064 ETH (0 + 0.242912275383967402 - 0.190813683190561002)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
111,843 bytes
Gas Used:
22,977,669 (76.59%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000008304309858 ETH (8.304309858 Gwei)
Burnt Fees:
🔥 0.190813683190561002 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,566.61 / ETH
Hash:
0x777f8dc1fe34a32fe1cb6e6ef3113cc310d479f156f7676051bf8f249539ce73
StateRoot:
0x95251ece1e200e0b4ba55048512c1a223d54d2370cd2cd7a2641211c92e393d4
WithdrawalsRoot:
0xf7a4eb0ffe3ac7fbf3c4306352a964ec9bfbc04ff5ce6406020d0b85ba5f3f83
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb08f01717bf09611f512be0f83eb71df4f947709b7bb02d2f77272cc0b1bb0f7
Parent Root Hash:
0x3b63bedcb4664db1051ce6a8bc474f7550ba8c55ef7cc45e2b5d82db0ed3ac3a
Beacon Chain Deposit Count:
1538543
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x49b76d994e422ca607678cdf3fd951dd57cdb4cc6f0ebb4f89fc48ab0a22d41e
Randao Reveal:
0xa1ef6ac61e897784ed008b9efe0d0eb549811b1d3d5d5a9ee0982f5cacaa05e21b431633c02efab854ee7ecdd5ed4cbe04c4c5185cc17a97d26f128bc71d41c49b47e03f4d897a3c7e8837f953e86cb1852a4dc30e83f703085c56f158b8e641
Proposer Fee Recipient:
0x518489F9ed41Fc35BCD23407C484F31897067ff0 (Fee Recipient: 0x5184...ff0)
MEV Reward:
0.056528972881476773 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
262,144 (2 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.