Block
#17981641
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
921 days ago (Aug-24-2023 02:39:47 AM +UTC)
Transactions:
182 transactions and 74 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.040199675352109778 ETH (0 + 0.307682452525539778 - 0.26748277717343)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
164,457 bytes
Gas Used:
17,449,250 (58.16%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000001532918476 ETH (15.32918476 Gwei)
Burnt Fees:
🔥 0.26748277717343 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,660.49 / ETH
Hash:
0x1394fed5c0f95eafc098fa35a7a69b642df27d0db4ec8ed5f5b4318a70bf2e76
StateRoot:
0xfb294baba6a586398470ec6329d12c07f14699190e5d15dd86de5f89cd3ce74b
WithdrawalsRoot:
0x267182b6eb10e46ef10939e60c883956278c8ac9cc7cd588ec9cfa708464d445
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf362fe01bb2cda45898027a7b05172bfe447e308c3b04079eb7fa593a725c726
Parent Root Hash:
0x937cf6ba99fb50e76ae067e8209a273536260cf7c055e9bc20d4b23c72a11ff0
Beacon Chain Deposit Count:
927228
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xc06a73603240ba9844a5b4c022ce152ca05c908bd91b8f5413fabd9c3b537a57
Randao Reveal:
0xa4f202fcddd9765afadb3a8077349b0cdf17b8c963b60fa206d68bf47a6132610c8b54f460aa1d3bc108825d158a18f0076c2b6be57ac74329de44e22addbc5700ae58c646f84dcbd6a9de74e57a7d225d08856cd39cd2e6a0a39bf28a98a21c
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.040335147526866136 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.