Status:
Finalized
Timestamp:
165 days ago (Aug-11-2024 07:34:59 AM +UTC)
Transactions:
123 transactions and 54 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.02076201968439537 ETH (0 + 0.03230455915216625 - 0.01154253946777088)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
53,821 bytes
Gas Used:
13,279,576 (44.27%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000086919488 ETH (0.86919488 Gwei)
Burnt Fees:
š„ 0.01154253946777088 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,555.67 / ETH
Hash:
0xbbfc0ec92497f9982cefd5a46002ab99fed8625aec29ab5d999d8598dc6ad05f
StateRoot:
0xfcc3a04236d84b1c7552471c8932fee73b7038c32ad66b704c95e10a02fb7885
WithdrawalsRoot:
0x5530da7d58cee0755c7768e5c9067e3edb63cd6f8d4919850c7247df147c4ab8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8085bf2b07d1ac53b12878c51d743092733054b1784518bbd08f36bea5f789c3
Parent Root Hash:
0xce39e8319a480df5a69882947d0802052fa2436977c1a3f80c5f42e901b82430
Beacon Chain Deposit Count:
1633629
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x568f61b2c76b509de19e1d1467cf74f8f21302a7656f86ce8b7a0b11825b48f0
Randao Reveal:
0xa23782d7b825b31764f662ae3bbdf1a827187211cbc5f169eebe3d58ccd97cccbccf3af9515165a56f53dfd73f7b1a4c0cd853a9254668cb3f2f53b00ab827bf8fe68000c9b91c3e8bb1804ef25da32e1ce9e3441893c12bd2400a69943a0393
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.017598749761618857 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.