Status:
Finalized
Timestamp:
45 days ago (Nov-11-2024 02:12:23 PM +UTC)
Transactions:
417 transactions and 144 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.067728816217336191 ETH (0 + 0.556382249816075836 - 0.488653433598739645)
Total Difficulty:
0
Size:
146,122 bytes
Gas Used:
29,986,051 (99.95%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000016296024895 ETH (16.296024895 Gwei)
Burnt Fees:
š„ 0.488653433598739645 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,375.79 / ETH
Hash:
0x9fde88a8b9ee56003ba641805a786b729e004a9093888c766d813a81e01d0444
StateRoot:
0x2575266b1a140431e53feac7674cdcde4ea561b94622fe3e835eee7cd3070fc4
WithdrawalsRoot:
0xcd3627cb5d8a09142c27bdc69c052d1ab66ad89893c0f4a7a441eba1c84f913d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x07edca0f555173f68c53542f7b3671f48a71c9de3250b9bd5bf8a3a64783b7f7
Parent Root Hash:
0x90f9957ba455c1700cce2f74da028574d0a564b53d50210fced8b658224063f3
Beacon Chain Deposit Count:
1765303
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xdc07ff1d2fd18122b4091086b2c04c8441a49663f918b1d7ddf9e40d27835ee2
Randao Reveal:
0xad85d5ed5696242ca398f59a4754376973d7d4b28416917882c4d2cdcc2e5258ba42d9e5267671c3509b5e58ad29fb20175366b9359cbfddcf2b1cc7850b01a7514ead46ef08547ac317751a616abee9ad1965e1bd25d33ce63b6475467ab516
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.079624007543163451 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
0.000000008063797892 ETH (8.063797892 Gwei)
Blob Gas Used:
786,432 (100.00%)
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.