Block
#18297640
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
875 days ago (Oct-07-2023 09:14:11 AM +UTC)
Transactions:
111 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.011991097589820247 ETH (0 + 0.073888284051176229 - 0.061897186461355982)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
151,027 bytes
Gas Used:
10,497,934 (34.99%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000005896130273 ETH (5.896130273 Gwei)
Burnt Fees:
🔥 0.061897186461355982 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,634.64 / ETH
Hash:
0x2276f1fc664f5f8f71b8af9d632cc518f5a1955da4cb216a5cebfa5f5e95a7da
StateRoot:
0x749863cb5b6580a5cd173c4358f510ad70414a12c4d035bcefbd67ac731fc4ff
WithdrawalsRoot:
0x91b25fb8353e141a6f341acd2d386ff288e50f6081a92306cc370bad1b0b3f7c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc2f0899bfb482a838561d4f007609c24447f7f7ca239efc0766dd8cf92cd64c3
Parent Root Hash:
0x2ae52964e39d00d8ea5d676e8279dbde0f2c52712ce9190688aa1c96380879ec
Beacon Chain Deposit Count:
991240
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xb801e18b0a12e18cb7def7d2de1564d8ad1c381d46970199a64c80852da19d8b
Randao Reveal:
0x96f1588c37a357369f2c9665881c7e44543a8550712ca158da1fa36f61d11f5fba2fe2ea37477b3497c100bf572fd60f01afacb6c4e96ce7fb39bb0c03b213862b86afe2011f741f22cddfcb04568b786c038ea0cd63855e7e86a085ef86b621
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.013348748015853944 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.