Status:
Finalized
Timestamp:
64 days ago (Jan-09-2025 11:07:47 PM +UTC)
Transactions:
115 transactions and 33 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.020004485156558396 ETH (0 + 0.070698202898297156 - 0.05069371774173876)
Total Difficulty:
0
Size:
46,028 bytes
Gas Used:
9,041,955 (30.11%)
Gas Limit:
30,029,295
Base Fee Per Gas:
0.000000005606499672 ETH (5.606499672 Gwei)
Burnt Fees:
š„ 0.05069371774173876 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,219.05 / ETH
Hash:
0xe7e13ed6b8c6e893f33f0b6e61b29806c0949b190f709bbefc435995fafd5aa2
StateRoot:
0xacc6d54c8b398e4f93cfd4af758e76cc04b1c96af6f9474d38db819346c0bcc3
WithdrawalsRoot:
0x51454a50cff7f30a895729e3f155fe1fcecd43f39ef8c76585a51875fd172d9f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5a693ef5b6781d39e76a91eb76b6c3270702ac3f944b7ae594172b427a2eb33e
Parent Root Hash:
0x086fcc85da757eb8c9642fa69c9fa596805e49a0a1ec6fc1c4123a153295aa54
Beacon Chain Deposit Count:
1858730
Slot Graffiti:
Block by Stakely Lido008 TK (Hex:0x426c6f636b206279205374616b656c79204c69646f30303820544b0000000000)
Block Randomness:
0x84e457d3b877037df06bd283ad40570c5f2a1b90d6d72d365c0fd09a75d94e36
Randao Reveal:
0xb2db71c6af43ed2fdd70be9b475d03f401d0813586ce6b57cb286684da4bdecd36c9493e34d77fddeec05f0e3478caa906517d77e8c3f4d30ad5721234d1514993e7763dc36f9948e85ea1857895f00bbac536c164131488ffaf8b5af2a712fc
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.020342271578801658 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3.00 Blobs (50.00%)
Blob Gas Price:
0.000000001224895904 ETH (1.224895904 Gwei)
Blob Gas Used:
393,216 (50.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.