Status:
Finalized
Timestamp:
158 days ago (Jul-11-2024 08:49:23 AM +UTC)
Transactions:
168 transactions and 49 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.088763900093842161 ETH (0 + 0.168759536620286761 - 0.0799956365264446)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
74,897 bytes
Gas Used:
16,591,285 (55.30%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000482154556 ETH (4.82154556 Gwei)
Burnt Fees:
š„ 0.0799956365264446 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,099.49 / ETH
Hash:
0xe3148b6e99bb58ee8f13aa172ac163698e81e3bf2a0b9ca1175b1f19bccad72e
StateRoot:
0xdfba4a86bed46ef9cb820da236df5a084e699d61844da23431caea653847cfc1
WithdrawalsRoot:
0x258ca7d3e91c08ff66d5a390117593f0936c9de6c5ec7afd8f2876201270138b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2fff919726510bd48eafa898f93c626505bce803a346e513b74951a2c8a4f16a
Parent Root Hash:
0x9a65fe064ba37f049e2c730ea6ac500f9aef20d4e00c24bfac47d6898d8881b0
Beacon Chain Deposit Count:
1578954
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xbd2a3ae8644e35f6d96b5aaa50d45752f2199bdb354c73bd844cff150ba960e1
Randao Reveal:
0x82383866b9ab48f86845fb3f0813c501a1fa9c644ce5376971ff2ec1804a6115a0c2ee16162fbaf8903d84ada7711e64035b92168e3cbbd06cbe7f11962badd22a89de84178a2f500524451b07f845a0ed002062ece3d4c6d5c824133d2da9ca
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.092367576250002288 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2.00 Blobs (33.33%)
Blob Gas Price:
7 wei (0.000000007 Gwei)
Blob Gas Used:
262,144 (33.33%)
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.