Block
#18246021
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
880 days ago (Sep-30-2023 04:04:35 AM +UTC)
Transactions:
157 transactions and 275 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.044153208728827201 ETH (0 + 0.164782562501437906 - 0.120629353772610705)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
78,080 bytes
Gas Used:
19,091,985 (63.64%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006318324353 ETH (6.318324353 Gwei)
Burnt Fees:
š„ 0.120629353772610705 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,670.97 / ETH
Hash:
0xe467192df670aaca40d16b949ccf0f08fa01121ac65e54d50bee3c52b2591bab
StateRoot:
0xda4830eca06c2d9351e402afd01c685370468d2636ef2498009c3dceaccc65a6
WithdrawalsRoot:
0xa9ea14a04b2b8ea17570433eaa8723b38cfaa543bd3765c3a9a8406858914032
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x0b256538f63c0361685985ea3ca4e7a1a3bb48dfc113b60985c709147d6f065c
Parent Root Hash:
0xf643a78537ac785d3f2119d27f9d0405b8d2f6e4b7281dd752173a58d56979e5
Beacon Chain Deposit Count:
981009
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x4c46bd3b9b703671e4b3eafde2f196575f23a05e6a7ed3c3e78927c16e94ce42
Randao Reveal:
0x912edd639ca1dba6e3ac8b6be1587e0cac1971feb20102a65dc263439c1c4bd31ec9f2e521ecdf18790aecb4a7256b721603e69ba94773fcef9df0abf42cee17bcfcf2bcb4a21f3a520fa7ff46cfccca5213b24dbccd6611c6cfeba642c85ce5
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.04470968281361248 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.