Block
#20176103
Status:
Finalized
Timestamp:
609 days ago (Jun-26-2024 01:16:23 PM +UTC)
Transactions:
185 transactions and 82 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.040155930909500366 ETH (0 + 0.132266495660152166 - 0.0921105647506518)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
71,531 bytes
Gas Used:
16,689,378 (55.63%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.0000000055191131 ETH (5.5191131 Gwei)
Burnt Fees:
š„ 0.0921105647506518 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,369.46 / ETH
Hash:
0x66b5bc06232d471ebc67cbeb6a52b45d48e631a98eb87515eb6303eb797f80dc
StateRoot:
0x1f4883da20cc434883cccd4fa9350f97d850fa616b1e8abcfe1c487d7b792acb
WithdrawalsRoot:
0x4596c15424326528fd78dff5878b42d9c97cb1e89ab897ecb38c280eb4f0169a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8dfa073dee690d196dac5cc490fa65e87d9d8dcc79a5d64cda46d60681b94c57
Parent Root Hash:
0x713fbaf20ab91360fde997c7e0a458ffac486e09c43405041825ac2c9c0d7200
Beacon Chain Deposit Count:
1559376
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xecf2b3244fee5b976b1195315ce1bd69dace5fa09dd8c84a207c70666b3fc7c8
Randao Reveal:
0xa217ca651a8f92cf23f98bb4b9a2b1dac80fa5141b7456825dd40cb9769373a2664b0e5ae37b0939911012289782bb610c5117fcb0043d3abdbc7190b0f0f7b600ad731c41c3d1fdc6198b0ad16e0ceec56b126fe008757fd7b92dc549c66c79
Proposer Fee Recipient:
0xeBec795c9c8bBD61FFc14A6662944748F299cAcf (Fee Recipient: 0xeBe...Acf)
MEV Reward:
0.028456718916132219 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000131072 ETH
Excess Blob Gas:
786,432 (6 blobs)
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.