Block
#20033005
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
630 days ago (Jun-06-2024 01:12:11 PM +UTC)
Transactions:
235 transactions and 70 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.051866221898089375 ETH (0 + 0.458637584370510715 - 0.40677136247242134)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
92,503 bytes
Gas Used:
19,645,365 (65.48%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000020705716716 ETH (20.705716716 Gwei)
Burnt Fees:
🔥 0.40677136247242134 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,812.05 / ETH
Hash:
0x6fb4a21958d97852489f3ce0e419b47049dc0ef041f7f750f66f48e40b3887a4
StateRoot:
0xa7cea0701671e5e626ec2c1f2e7b2490ca421b5b3ae5d0a0252494d3bbeec803
WithdrawalsRoot:
0x10334dbcd27bcedd395e5e80772d510aa63454fabb453c338691bb9b4ad1dcdd
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x97be98e7a64a98513955a89267b010fe0188bf4583b54cf0b8c6dd2fe277d5bd
Parent Root Hash:
0xc8dcd9d9f3998db0389fc2f80ff79acd85948d2e8646f5d452434102f1ebb449
Beacon Chain Deposit Count:
1518309
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xc2be84e0ebffb633ea2d84d348acd32073a5f2820b041878b79ecd5e86e8a49a
Randao Reveal:
0xb15b50ffb3e5975622ebe82546f03235d6d6eb0f1c31f0e58c934c3a18c4269482ebe0df6bb6485b707e7ad879ee475706ad8a3c71e6707fd19993bb1ff3fabeed1d35fe134d789aa9a7bdf655c13faf56d6e4213d36a98eec97da137baf8cce
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.062315947255191288 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
84 wei (0.000000084 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000011010048 ETH
Excess Blob Gas:
14,811,136 (113 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.