Status:
Finalized
Timestamp:
70 days ago (Oct-01-2024 10:52:11 PM +UTC)
Transactions:
215 transactions and 109 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.131594537079915936 ETH (0 + 0.298623738443909254 - 0.167029201363993318)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
113,090 bytes
Gas Used:
24,123,491 (80.41%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006923923298 ETH (6.923923298 Gwei)
Burnt Fees:
š„ 0.167029201363993318 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,447.54 / ETH
Hash:
0x5a20ae950fbacb9223647d71861a8d950d87f6a145ea645d97e9d900071f4a93
StateRoot:
0x3668f1f33a02e329cbcd09a20627f62804d1abc47f5c01838a6cb398a71ed04d
WithdrawalsRoot:
0x1c18743035fc56f2496590646bf92eac6c025f80bc8fb9c8e82f6dccd4b7098b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc64860c099722909754222bee8a3d5fcab5ba2af00c0f27e99664c68a5803113
Parent Root Hash:
0x79b72cadd5b6c904030fa1ecd24db465b6601b01419e34725ccf341ffbedab22
Beacon Chain Deposit Count:
1699954
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0x432b65f1867b6dd9a417dba520a48a86f597d4578f14403761762b7b3795d528
Randao Reveal:
0xac9b7e917ec2a12e4f5b47b57ee2d088f2b10ce20b07446a13a3f4ad60480a6ffc184d1f43fa2b319e07f829532af4931645bf9eec17ff68a1a5ce5fd129e71704f78e30dc4a8b759566427aefb3d6a9c77af1f503594cd99e3cae470b459f06
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.120319002382204296 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.