Block
#19072452
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
762 days ago (Jan-23-2024 10:52:11 PM +UTC)
Transactions:
22 transactions and 14 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 24 secs
Block Reward:
0.043750153966407156 ETH (0 + 0.077056061647012156 - 0.033305907680605)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
12,322 bytes
Gas Used:
2,574,068 (8.58%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000001293901625 ETH (12.93901625 Gwei)
Burnt Fees:
š„ 0.033305907680605 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,241.32 / ETH
Hash:
0xd835ad682ed44b3e3dafc607db3a6009e4ea369dce5e28baafa97a22249b61fc
StateRoot:
0x03807c29f54064750ab41eeb8d457a3a724cd0e3f9b061d696c75d4776639cd3
WithdrawalsRoot:
0x5a18d4acb197f6b666f9a8c629f5d30fa637fd7800a7ef35df6501f2701de343
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x323204441fe25185a548e2f3bf07680263bbefc6e551f0b91749fb45ebfb2b87
Parent Root Hash:
0xe1fc640a0d9696e009a40e2bce19f4010bbbd5ca3de15bab8a1810fc6278978d
Beacon Chain Deposit Count:
1187842
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xff987ca1bfb22cb512f6069228aafad0dae9acf1d9e138ac69f5b4cdcaf751ac
Randao Reveal:
0x87d55192bda679501e760f71240fe057862001682f9f85f822b87853e20155e74064a40e297c2b972fd5032650626b0e0f73e30838c24129cc867cd24c61f7a4ac916a2c2dcb6dba6d4a01b226acca0b67a11e606e24734e09e4f95d3ebe5c5c
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.069638565747301888 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.