Block
#18473483
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
847 days ago (Oct-31-2023 11:48:11 PM +UTC)
Transactions:
208 transactions and 82 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.041817968140325223 ETH (0 + 0.262199977451954148 - 0.220382009311628925)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
171,727 bytes
Gas Used:
14,389,335 (47.96%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000015315649355 ETH (15.315649355 Gwei)
Burnt Fees:
š„ 0.220382009311628925 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,815.45 / ETH
Hash:
0x3f762f87db7b9919722f9c2112599ee247589e9739af84a0fbece48e3b828fa1
StateRoot:
0xa5fce1136c8237468d9d2fe8e571394d139393170be9c7573f9cb1b2c2a3d07d
WithdrawalsRoot:
0xe731361d7566123bdc7bc77635f39d77a01c6eb503879ea2f7767e4840a305b3
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x25126766811c55ff48d2bf833a7d62c449a359b02df3d0de97c7d7d815f6e00f
Parent Root Hash:
0x0f4b75a898de82bf624ea64dd3c858650bc6b7dcc50d9eb382e5b5c25f5e84b7
Beacon Chain Deposit Count:
1030089
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x9227f6a47ec8ee560dfb57ea6e43e6f2127e293f014bb9a8283f44193b609044
Randao Reveal:
0xacd534847a3b503c11746a67f951afb39d58772579b53680844d7622a7fc716d51e533f4cafecebbb568c1824ba388720327b8a8070182ab12e45cc5d82eb143ff65f601268d0cca6c76025f3fdec8a95ee84ce4b9f3f5c3ae799f5be5c30a54
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.041879323817436818 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.