Status:
Finalized
Timestamp:
97 days ago (Sep-18-2024 03:56:35 PM +UTC)
Transactions:
164 transactions and 66 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.068089509436163496 ETH (0 + 0.263029564533377496 - 0.194940055097214)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
77,812 bytes
Gas Used:
13,851,600 (46.17%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000014073468415 ETH (14.073468415 Gwei)
Burnt Fees:
š„ 0.194940055097214 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,375.01 / ETH
Hash:
0x55e16d7783faf4a1da9a09b0e93a51a3383b68cdbc96b1101787aae803e63e0b
StateRoot:
0x2af64c0a64565cee21fb4dd2db76df5e9dc76fe69361697bceb562a7364b2f7f
WithdrawalsRoot:
0xcdd27deb79a7c50d5d451281b338c6b5f454788677dcd9e2883f16ebc6f38666
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x0e562e14c608e1af2e8c9c6e766115329b1391358f97b4366f28c946fd8fcf5d
Parent Root Hash:
0x325f63d57328de04119508a9e6eb74312e9ea6ec1172c747fefae9687fa8c541
Beacon Chain Deposit Count:
1686241
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x46f8c1781f656c45dfec9053aab89e0e073718612a759f33aae98d838adcef4e
Randao Reveal:
0x8c77c8f0cda8aa8764d1f50f46b06f964c9babfecd7e7f282091c86bdd48d85cb1b7698c2adafe94127699f6d4bb319419f2ff99d76c11bd5ef329ab8ebde6c430319f97e4641ba6398a3c4bcd184f042e36a8975aa843621ced6ef01f1edad1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.060760212622470306 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.