ETH Price: $2,396.64 (-4.32%)

Block

#0xe26f38b32229fbfc9ecbcf707387aca350ed9ea85d03f00754e36d65916c614d
Block Height:
18531647
Status:
Finalized
Timestamp:
300 days ago (Nov-09-2023 03:15:47 AM +UTC)
Proposed On:
Block proposed on slot 7722977, epoch 241343
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
Block Reward:
0.028354807748742685 ETH (0 + 0.496740725602219779 - 0.468385917853477094)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
160,333 bytes

Gas Used:
13,881,451 (46.27%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000033741855794 ETH (33.741855794 Gwei)
Burnt Fees:
šŸ”„ 0.468385917853477094 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,121.13 / ETH
Hash:
0xe26f38b32229fbfc9ecbcf707387aca350ed9ea85d03f00754e36d65916c614d
StateRoot:
0x31e81c6215d0fb1fc471ffb6197a570513ee4391943652856120b6106a2536c5
WithdrawalsRoot:
0x224b80e2871dcc92f4c02bc542ecbdc44ab8e3f1f52ddc3ada229c101e1668a2
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0xaff1935cbbf225af2249827c6ddae1c9ebe94083f405fe26fe9db0a2519ebfa9
Parent Root Hash:
0x7a5d0082114a138db2e8ef5a819be90c7f4f58affbce00478b5db933572260f1
Beacon Chain Deposit Count:
1047043
Slot Graffiti:
Block by Stakely Lido011 (Hex:0x426c6f636b206279205374616b656c79204c69646f3031310000000000000000)
Block Randomness:
0xfb86581ded8f722869c00a554a081d4642543beb363de6751972d29a819e12dc
Randao Reveal:
0xaaed5289722e6eb80c776fc5e5d3c849fb119c9803df7d75e00a7dad19c5794639789335025f41f5a95965ad2825ad1f11c86fa1acb619120d829013a11cd3daeeb5f23c3a4f6fe18c0c61df195b4af302956a7f56550dac70ec5a73fffadb17
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.028176077021391551 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.