Block
#0x4ee88903bef4b5c7b25d11c03ff69d535b72cfb6fb821cf20e463cfa409ea5ed
Status:
Finalized
Timestamp:
131 days ago (May-25-2024 01:35:59 PM +UTC)
Transactions:
156 transactions and 38 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.049293418666049311 ETH (0 + 0.125695982285543343 - 0.076402563619494032)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
74,453 bytes
Gas Used:
13,460,731 (44.87%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000005675959472 ETH (5.675959472 Gwei)
Burnt Fees:
š„ 0.076402563619494032 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,749.23 / ETH
Hash:
0x4ee88903bef4b5c7b25d11c03ff69d535b72cfb6fb821cf20e463cfa409ea5ed
StateRoot:
0xebf9cc32b99cef5eab8c95095313b96b9c037cbd9817034121ff12889c74adb5
WithdrawalsRoot:
0x5a60dfd1120dc1ebcdd41f9305273d1670f148640cf932c67da25ae7d51f049d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x301b8c1a411afb9b0ec62ba7446297255becfaef3b5d4421cb2c50769c10e05d
Parent Root Hash:
0x5f4eadc002b44d45f0bc3e1c723bd917f7c366f1ef817c91b3849341f0eeea0a
Beacon Chain Deposit Count:
1488253
Slot Graffiti:
Block by Stakely Lido017 TK (Hex:0x426c6f636b206279205374616b656c79204c69646f30313720544b0000000000)
Block Randomness:
0x36d9a743db2abcd0acb8ca8dc2c5ee848d327ff56acd259d449a384734a2e613
Randao Reveal:
0xa952bfa8f2761800c8230c78795e0158971cc498fd5bd45a8da6b51b38a45b23f569716b72572b04262aa9e4f4ae68e413ac1e722a0947f1de5e5783ba0badc9977748512102e8f236828c2671fc3b6b0c09be925ff2a0612085090de41774d7
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.048250040321155262 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
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.