Status:
Finalized
Timestamp:
55 days ago (May-04-2024 06:18:11 PM +UTC)
Transactions:
245 transactions and 144 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.076837724850962501 ETH (0 + 0.184469038801281233 - 0.107631313950318732)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
92,833 bytes
Gas Used:
21,800,547 (72.67%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004937092356 ETH (4.937092356 Gwei)
Burnt Fees:
š„ 0.107631313950318732 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,117.52 / ETH
Hash:
0x73c95b67f907fe8f5b1cb9a2ef6ae6281e81b8ebf4009a94705ee64e02df8827
StateRoot:
0xd1db061272385e1a8fb998e18287a54367239f276bec573e046d6dfbdf4e77c9
WithdrawalsRoot:
0x41ac28cc85a1fb148e78f3939cf4e0cd028526db5563bb76ed43895e06ae767e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x466172e4f36612698ffa185913d234fdafe9e4a1bb21b9b064a6e16eb84b14dc
Parent Root Hash:
0x4f6e58f2e7deb02a68c47fc11ec9fd06ef5e7f3cfe78502c9e2e8ed74a35c09d
Beacon Chain Deposit Count:
1463278
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xb9f7f396217105cf50c8f46ba544975a20eebc1f29e6b59426e32ad24c41591d
Randao Reveal:
0x83864eaea531bbbcc05d0fb934850bcb0c3ee2a0e984417e37c96f9434f64c639a95fee7500c466ce0987abd01a5aa050363f5587d643799397b095a286160ffbd67432ded0c50a1d21c721bdbacf90f3f4bcae61ca8e54b06b155e3bc59c3ae
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.078278662592680718 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Blob As Calldata Gas:
1,119,152 (8.54 times more expensive)
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.