Status:
Finalized
Timestamp:
82 days ago (Sep-12-2024 11:00:11 PM +UTC)
Transactions:
292 transactions and 202 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.060274117045739155 ETH (0 + 0.114349772183612083 - 0.054075655137872928)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
116,486 bytes
Gas Used:
28,980,942 (96.60%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000001865903984 ETH (1.865903984 Gwei)
Burnt Fees:
š„ 0.054075655137872928 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,361.91 / ETH
Hash:
0xddc27e3892250e82a1b5f127645befbd3b687a0417403275130ebabfb3856e37
StateRoot:
0x842622800afe8f04d4886e3a776ff728c215386a8624386bcfeda6e5dde3383b
WithdrawalsRoot:
0x3489588b7868b099b9495449e9e28a26756a9530ada2da41876f2246707f8cdf
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x38e0f3db860958545d4dd5f048ef340548519c6aeb9937ab956ff909ec1602e4
Parent Root Hash:
0x9ae9ee1f41ef8528086720f6a0aa81fa5a7e304a772257a87e7ec89aadc6ec0a
Beacon Chain Deposit Count:
1680008
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0x601ccb25d89a889349fce22d86ef1e5c7f2c79b9ba1f86d4d5ff07194d8cbdbc
Randao Reveal:
0xacebc2a9d1c6f258c33847e794fe41f7c91e9c38f40e19cd6f7ed5f5b2e88e9989e49772965cdc4979ed35d35931738107af11266fb8fe75405d67a27a36c87c6258f7a5b319e7aaf9afda4eeadd6a9d02df00063787672352347dd19f87ca3d
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.288938127837594152 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.