Block
#20170852
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
607 days ago (Jun-25-2024 07:41:35 PM +UTC)
Transactions:
220 transactions and 61 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.047334793150811924 ETH (0 + 0.149852376490780196 - 0.102517583339968272)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
104,705 bytes
Gas Used:
16,176,818 (53.92%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006337314504 ETH (6.337314504 Gwei)
Burnt Fees:
š„ 0.102517583339968272 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,393.91 / ETH
Hash:
0x04922ee74e9a5d78632efcee3a0f0c129e4ae22c647845ad3df606da5c87835b
StateRoot:
0xd98848d85f22a49f21b09fe4c2f34b1e64303c81fb739d356e89ee4ab43e6bf2
WithdrawalsRoot:
0x0ee63771ab24455960b5d254d1df31e6cf06abd0c0d11bc3a5f318240a7af643
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x6269978bf8e09d85816455919d48730cfb472caf6f25a73b6c6c091e0dc0a574
Parent Root Hash:
0xa5e224907fcbce0b9e6ab1bfb3a7cc824e2c99b938e937377659c8e60aa6f235
Beacon Chain Deposit Count:
1557748
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x779f4b4232318230f9e877f1b0427d0ece405ae94a5170c9cd3370a3b760bdf2
Randao Reveal:
0xa2d204ad16cc2e0b965dccf31173f015c93a4ed6ee100291ff9f70cec8d916d3ca36e31c89dd878fd34394fff0151f78183b121f9dd4951f653f70c872bcdd66207698c919d8783927a2138cc692885918d209f0dd5222a76bc2b0a428474ff2
Proposer Fee Recipient:
0x7e2a2FA2a064F693f0a55C5639476d913Ff12D05 (MEV Builder: 0x7e2...D05)
MEV Reward:
0.048818542958242258 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:
1,441,792 (11 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.