Block
#17623187
Status:
Finalized
Timestamp:
1000 days ago ()
Transactions:
65 transactions and 29 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x563...cf3 in 12 secs
Block Reward:
0.008780088845471792 ETH (0 + 0.346965655464394449 - 0.338185566618922657)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
29,482 bytes
Gas Used:
5,780,287 (19.27%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000058506708511 ETH (58.506708511 Gwei)
Burnt Fees:
🔥 0.338185566618922657 ETH
Extra Data:
�geth�go1.20.5�linux (Hex:0xd883010b05846765746888676f312e32302e35856c696e7578)
Ether Price:
$1,936.34 / ETH
Hash:
0x994d22f6e95bf3b036103a01f00335126fcfce0616f5a1c8d5fe991bbe55f1be
StateRoot:
0x585d0e95bf5d3f890fd5605a2e516fa69f9ca27a9934a85cdb8bf7caee81ba08
WithdrawalsRoot:
0x479d7791445327f2c39868255b08b18a33e8b66a59d764ea08cf80f2c08ad9e6
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd135f681992c6ef594c8857767edddba5f9cad95c2ce9f8ee5a8cd0252e14651
Parent Root Hash:
0xa0b2de3f29bfeda6b1b27302e72c655a8d8ff1047f6d0d242963b677e1c96a37
Beacon Chain Deposit Count:
838870
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x1093fee7f1cbb2f757fcbee73e814b98a92a34d6d384903a4705dce1fdab3631
Randao Reveal:
0xb7da74dd18d9acc3179706fdcc052f58889e487ab45b7539fa729baebe181fd491616c5820bb984c052f2f0f689db8c60d34d2fc23e757f303e052f8616772d37da3bc709b9d98a18fa8efbf895b12c6a5fb96f71319936e35f4a30941319e1f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.099593470259423702 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
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.