Block
#19084611
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
762 days ago (Jan-25-2024 03:45:35 PM +UTC)
Transactions:
156 transactions and 45 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.078467742415430473 ETH (0 + 0.662798923398831305 - 0.584331180983400832)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
77,341 bytes
Gas Used:
13,320,856 (44.40%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000043865888272 ETH (43.865888272 Gwei)
Burnt Fees:
š„ 0.584331180983400832 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,217.50 / ETH
Hash:
0xfee10b16f3d085ea1356d7d1a10ea449d2084146d9c6287c06efa24db69ace4b
StateRoot:
0xd8e4d44ab212c41fdd3bb602df12798b2d45467d5d86aa74f24a844b054e17fb
WithdrawalsRoot:
0xf29c89deeae3f892ed1b0ddcb644eb9bfb5ed8c9c59004e98cf393420fc38bb8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x495d2ca32cc0f33e1ccc8559027fabf603a4ca96a09d0a390f2168aa68cf8863
Parent Root Hash:
0xc4fa2b07aa0d9db052fd705627a01f3a9055fbb9dbe4c59d800391103b46359f
Beacon Chain Deposit Count:
1193250
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xff3bd40ef56ad6f1a89f1d14ed4d6c02382be095072117d4c9ece9d258e2b12b
Randao Reveal:
0x87536da76ff0973108b1926b4af8a0630d1382871deb680eda9390635cd722f576dd8d103fc93ff0a90dd8e19e464b1500c8e818fcd8bfa28d67b1bdc252011432cd0eed9c15809495a4d83657ab438d7f4948f53d725696b44773dafa72e2fa
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.143301925373014259 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.