Block
#20068093
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
624 days ago (Jun-11-2024 10:49:35 AM +UTC)
Transactions:
116 transactions and 109 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.044097276879680932 ETH (0 + 0.174798690428667783 - 0.130701413548986851)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
51,833 bytes
Gas Used:
12,023,519 (40.08%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010870479229 ETH (10.870479229 Gwei)
Burnt Fees:
š„ 0.130701413548986851 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,497.32 / ETH
Hash:
0x574b9dcc18ac6fca4c67c56996f979a1b845e54c34002948930c1a65a588fc00
StateRoot:
0x8c4bb6f83a2336ed258c30e98830bdf6ac10484a226e4e1a3d6574e0ba4c82be
WithdrawalsRoot:
0x314ec32391f1f0b58576ae95d2640b9203d7a5a6d14e5d62eac9795a5d9c866a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x674d5ef2c23d07b29d13e2161fbc4b02c98beb734ce39fd739c2e40f4b5e08a4
Parent Root Hash:
0x5a5435799f1a08fc3d1e0f81b1c87411a5ec715b42eb02f3a227fbc6b7964db2
Beacon Chain Deposit Count:
1528231
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x465b6e994e463f7c904402e2e0596b241991d74bf7a2a9e62582b89a3008b520
Randao Reveal:
0xa4a8b450c1e5ba46daf99acb7217f5cf39cf7a3c64f9b7b7e9e114282045a36c046b402ff4169d2b9db86aa1ccc05814193b72fd72d425e4ecca8dc572356c88c7d3dfdfb1640e4a417c1bd02f12a4c54b143f203c44d4d955688c0756fa9acc
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.102459796361162544 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:
1,310,720 (10 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.