Block
#20234845
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
606 days ago (Jul-04-2024 06:09:47 PM +UTC)
Transactions:
153 transactions and 53 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.860717723924682704 ETH (0 + 1.038959588707601704 - 0.178241864782919)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
91,919 bytes
Gas Used:
15,146,845 (50.49%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.0000000117675902 ETH (11.7675902 Gwei)
Burnt Fees:
🔥 0.178241864782919 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,058.81 / ETH
Hash:
0x8e5bd1e865b28f93668b8fa85a22fee214e3d1da995c672f3aabbed3729da8bb
StateRoot:
0xfec63cfe82539ebc028f0281a5aa798cec444365707f30f2f1df04bd54e5e871
WithdrawalsRoot:
0xfdd2a516fb2beaf33d83d563441415ccddce68f9072dd94a2e4bb72642fb6117
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x443a60827529f0580206a458954ed5111ec4fcccfbfa2ce2778ae3d73034764b
Parent Root Hash:
0x16406beca46658d0bd7563781e9db1f3e6d370f6ec09644fed9bbec67e65ee26
Beacon Chain Deposit Count:
1571134
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xb00b9d2dbdd1eb8604ee9ceb2a62553e71bfcf43067c190ec737994187af3d5c
Randao Reveal:
0xad7daf8f21f398012f7fcce23a5fab6f8a6c3bb7742cf11bb82027035809471ff7a55b039465bd544fd0c29c893819f70a6b744dd9c39e703bc7d79f3250aa5a025dde34e55eaf41c4548628edfefc3b0e284005c0e10b0522be5e8c77e8f990
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.868008971536549252 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.