Status:
Finalized
Timestamp:
95 days ago (Sep-19-2024 05:21:47 PM +UTC)
Transactions:
170 transactions and 87 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.048756805410571707 ETH (0 + 0.324484300925027003 - 0.275727495514455296)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
65,936 bytes
Gas Used:
14,232,023 (47.44%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000019373738752 ETH (19.373738752 Gwei)
Burnt Fees:
š„ 0.275727495514455296 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,465.83 / ETH
Hash:
0x4dfe3161469aee3aecebad4a709bdca856119f23cb4f45a951e58637d889f53b
StateRoot:
0xf02bb512c75644c3633f3d8c9cc64ddb16f106b3cf02809e26601d700dad6658
WithdrawalsRoot:
0x3f8356341f69d5de5fe6b19294b04154e574084bbd2ad7da970a0d9f59a7319d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x046cbc8949b8235db6680f8255c7c0cad2c97fafa60733114d82b1d432f11c50
Parent Root Hash:
0x654aac72482280cf69563cce0b2ce7e247e50442189b7fa109e964d90a2422dc
Beacon Chain Deposit Count:
1686931
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x633f3a13b4ff215559948aae611bc586e86f31c6f191d66ff0aa9d4fbf524dcf
Randao Reveal:
0xb075049b37e7c48fae31971e6f06c1a167783f3aa6b920be902e00fbda7d3bd3aae8ddd629d89504c9ec952dc1c4f9871631c51a84b5137cdd80d342db959d2e4f92217665c0b8fbb6b300f4bd14ed14b3536ada67903b5168f4850d0143b283
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.048893647992021831 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5.00 Blobs (83.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (83.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.