Block
#17319989
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1012 days ago (May-23-2023 05:52:59 AM +UTC)
Transactions:
208 transactions and 89 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.113593766374901122 ETH (0 + 0.703386057150258242 - 0.58979229077535712)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
132,283 bytes
Gas Used:
15,693,920 (52.31%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000037580941586 ETH (37.580941586 Gwei)
Burnt Fees:
🔥 0.58979229077535712 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,854.47 / ETH
Hash:
0x8a58fd82da2adeba7d46258d2d09ba4266d6e8b3a7f27a6b2ad3e59c136fd8f2
StateRoot:
0xc1e268208b7fac086e09a53a5f49437c0e828bc19e16b30e93e2a952d9dc6a12
WithdrawalsRoot:
0xa1c25894d30d43625ba9a6bc85224b4263dabbcb3966d784a4ef9c7079f8900b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd0c3959218f9d272cc62c51ffd316b5cc8f1c7e5cf6068d057d96ad520a5c1b2
Parent Root Hash:
0x03377de8fd1df3af2eeada9e3586de5bf026b459bb611f544ad348f9b33dbb29
Beacon Chain Deposit Count:
727887
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x0909cfe15571c17f88a9b862e06fbb0b008fd19776af0ec2dbe595023e68d7f8
Randao Reveal:
0x9912b550cd18a236769a80c463d665abcab596c0e0529b5a6d0904dc5c32e346f491ad86671d48498dba53daf77dc17112c551908a67803c1b7782e0a15eea3ebb8f6c5f2e421a7ed7300a986e4ba5ef24864ecd3a4d99d19655b2d3fc79d553
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.115190041031733024 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
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.