Status:
Finalized
Timestamp:
221 days ago (Jun-09-2024 08:35:35 PM +UTC)
Transactions:
161 transactions and 62 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.087454614275373211 ETH (0 + 0.228383513801171947 - 0.140928899525798736)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
62,752 bytes
Gas Used:
13,607,088 (45.36%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010357021247 ETH (10.357021247 Gwei)
Burnt Fees:
š„ 0.140928899525798736 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,706.00 / ETH
Hash:
0x60bc57f475a678e57426a06bda06af0f17ea0507c605b9fd91f2c886b7c2875f
StateRoot:
0x86412452703d6a6d8bc044adc5518cfeb60c29b0af9acfbe9a86352d9ca901e8
WithdrawalsRoot:
0x333dbbb1369fb33030c2d56741bec61ba4dc8667ddc0b90f18750ff9580012ad
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x69d68696b64873858a6af68d24626865986c78e9946804841343d518d2174715
Parent Root Hash:
0xf3891d086bb18315599b2d5f70ba79a4f48fcbf2b4caa013bad828d8e385b57b
Beacon Chain Deposit Count:
1525193
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0xa11a4ef7abd3965cacc01eae8136a2d0c1b6040087c5a01c12df6cd9aaabb90b
Randao Reveal:
0xb5897e001aeb90befe709b1135f35fae89c5cdcbdaae6ad65613e35136d4574a74b2d5267bc2f6c42c2d57f3d44a75650bcdd52de80eac5861a7c1dd31ebda0d40fd1478a5680bf04a03ec2c9af8ea44ebd9aac4b7011ed290aa325ddb7e4ed6
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.072963939536469313 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1.00 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
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.