ETH Price: $2,596.48 (+0.82%)

Block

#0xd7346ae35725dc57a4565f9281a1e5dbdfa9191f0d4ef8b218557a7cf1340411
Block Height:
18927986
Status:
Finalized
Timestamp:
230 days ago (Jan-03-2024 04:21:35 PM +UTC)
Proposed On:
Block proposed on slot 8122906, epoch 253840
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
Block Reward:
0.110198776908895333 ETH (0 + 1.400508108172988389 - 1.290309331264093056)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
230,859 bytes

Gas Used:
25,775,488 (85.92%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000050059550037 ETH (50.059550037 Gwei)
Burnt Fees:
šŸ”„ 1.290309331264093056 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,210.57 / ETH
Hash:
0xd7346ae35725dc57a4565f9281a1e5dbdfa9191f0d4ef8b218557a7cf1340411
StateRoot:
0x5655fb0ff81a602b31ee568f45888b4ef4956e82d25956155ee6746af0566588
WithdrawalsRoot:
0xe456f723b26d46bc59ce844fb076fa981024c1773cfdcc90240f99f9f6e168f7
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0xa1000fab3f74bc3cfe5723b5e3920fd69c0f669aac7c5de233388e2ae559ebc0
Parent Root Hash:
0xd7496ea570794af5181ae123a74aaa5cc0463c084eef6f65856389b6f3781bdc
Beacon Chain Deposit Count:
1149962
Slot Graffiti:
Block by Stakely Lido006 (Hex:0x426c6f636b206279205374616b656c79204c69646f3030360000000000000000)
Block Randomness:
0x18fe38269c66ab267be1b3a2c699c87da11261a4562e3f13b98705fd772f80a5
Randao Reveal:
0x908db5b2f0867c50626f606947b83558723218a758dc2280d6e5aea704812607b48510c83852ff32c26e4c0635bcdfc70c8fd3c38d92271d7b6fc765fbbe5836c3372bedff735a9e76430bba884ce9aa9a649a35bf830a9142b510817048e4d1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.375326058321694516 ETH
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:

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.