Block
#20376728
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
606 days ago ()
Transactions:
189 transactions and 98 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.0598418626973432 ETH (0 + 0.140837514881313059 - 0.080995652183969859)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
64,684 bytes
Gas Used:
14,544,141 (48.48%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000005568953999 ETH (5.568953999 Gwei)
Burnt Fees:
🔥 0.080995652183969859 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,335.15 / ETH
Hash:
0x34502b92d5ce7ce0e6d3feaeff8ff65c4a966cbe759bef71bfe1af236accd674
StateRoot:
0xac108a0d6ba15f619d042617d37fcc8a1f94b635bdeefc1bb0e9eb7b7dd1cd42
WithdrawalsRoot:
0xc3b9dfba902e93cd835f7d2cd80ff23da81eb024f6dc0dc18f44904d3988d582
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x303d925a260274631ddd2d217b36107c26bbef886650f9854cc44a87d4ced058
Parent Root Hash:
0x872e58c0f3f9d53ded8bcfcd19cff8d2133691cf29f7c7b424991caf8e6b6a56
Beacon Chain Deposit Count:
1605828
Slot Graffiti:
Uma got Prysm ready for Rencun! (Hex:0x556d6120676f7420507279736d20726561647920666f722052656e63756e2100)
Block Randomness:
0x455b5a0c3784b4aec3625826f0c39c6d4ef585ccb1d6d5f55588c703a7df1eb0
Randao Reveal:
0xa499e7a2eae54ed55152f7981ffd1be186e894862675f8d73a52bb2807b376fa36773137ac812cf549df098b296191240276784178603955b3676649f32a31ee2b276d212ac8f021b75fb69bbe3ca2ff43b05aba28913069bb60bb1f84d887c0
Proposer Fee Recipient:
MEV Reward:
0.038840781951736518 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000262144 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.