Block
#17177958
Status:
Finalized
Timestamp:
1045 days ago ()
Transactions:
149 transactions and 97 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
bloXroute: Regulated Builder in 12 secs
Block Reward:
0.057026044766188186 ETH (0 + 1.285431659744052301 - 1.228405614977864115)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
199,278 bytes
Gas Used:
17,879,823 (59.60%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000068703455005 ETH (68.703455005 Gwei)
Burnt Fees:
🔥 1.228405614977864115 ETH
Extra Data:
Powered by bloXroute (Hex:0x506f776572656420627920626c6f58726f757465)
Ether Price:
$1,905.90 / ETH
Hash:
0xd6b3c02ee524327db206789e0398329bf38183bf755f70962ffcb3d1637a8453
StateRoot:
0x7c451b28ce602267fbeeb8a4a10fddf5a93b694da1fff6dc501ba8aa799cb8f9
WithdrawalsRoot:
0xd8cac1b7f95c703013e442860e6e4c2a6437bbfee9bba82c2d3584d2d92478ba
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x389225686fa6c018d5529d0c67244c034adc5c6cad745b8f61b453be63ef1aa0
Parent Root Hash:
0x614c657ebcb0763b18c4df9c5fe100d2bde92367b60fdbc1d63f5ef0ef4e0fb8
Beacon Chain Deposit Count:
639538
Slot Graffiti:
poapqFgrWg9hW8Idd4BhhVcEK+YLMu0A (Hex:0x706f617071466772576739685738496464344268685663454b2b594c4d753041)
Block Randomness:
0x6ff330d3e9bae05d90c587903614cb01bc64b1d716903bc4d3b99c96b072bbbc
Randao Reveal:
0x84714a9522592ff31bfbaf94f44d2df0831f81e27d5257c63ec9b686b17783c7978fa8de587891591f921157f24fffd60672e7a6477ed47ed1cdb1e7a25ed99faf2abcb721e993b8ae735ee94557fa9e3a6fe1df815354749b00c3a5fe866437
Proposer Fee Recipient:
0x9f4B4CeCa7aCE96834Bd2fcC961c772De7cb481a (Fee Recipient: 0x9f...81a)
MEV Reward:
0.055583272211083186 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.