Block
#18583687
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
830 days ago (Nov-16-2023 09:55:35 AM +UTC)
Transactions:
138 transactions and 43 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.092567287067020495 ETH (0 + 0.407982286290559802 - 0.315414999223539307)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
60,332 bytes
Gas Used:
12,118,313 (40.39%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000026027962739 ETH (26.027962739 Gwei)
Burnt Fees:
š„ 0.315414999223539307 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,961.54 / ETH
Hash:
0x56fe153a506be53ef0fa78fcb454e385a40cdd083b0c853287d7189d34ca8e2f
StateRoot:
0x35d919bcb3b2ea96db0701431dbb367d95ca9405da71dd1b73b88b881a927131
WithdrawalsRoot:
0xb8c05e048da71208ee62cf7fdd6fa1f633c86c639b62b2b1e328adf56f98664c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x531825c8efcd04a4a41c4fb521be2efa5f2b93bbcd7af6c47d60e4b9fd6f0e4e
Parent Root Hash:
0xc71e5e3a912d5b15837bdc104916e5073cb5ee5a548cb39538bbc2ff2e303db4
Beacon Chain Deposit Count:
1061175
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xf1499e6969ee660bbe4b3beea67d31aaadc34274b77dda25405f9ec2a7f1f01b
Randao Reveal:
0x95d2a8c292d0c0c7ce7d744de2c175ad20ee1672df41f915d7b7ad4ed5990b7bed11fc6402c990944122eed6bb1c2a8d0c6a32dc2b62e7c92a20dd477ea3a27cd4cbbbb4f39adbd44a11e35394c4ea8ab5bb9c603cdb35e0d672ed2755f2bd39
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.093073970412198466 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.