Block
#17202201
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1036 days ago (May-06-2023 02:39:11 PM +UTC)
Transactions:
205 transactions and 106 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.06360652353524527 ETH (0 + 2.257858799691275605 - 2.194252276156030335)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
70,652 bytes
Gas Used:
14,545,545 (48.49%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000150853905863 ETH (150.853905863 Gwei)
Burnt Fees:
🔥 2.194252276156030335 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,901.99 / ETH
Hash:
0x5a3c9235b282c3b25c10db9151cda7bfb23995283fa9bd3e22e5c1744d48fa50
StateRoot:
0x2fa661c6a63ea9e761b9da3fd3aa0324318c298bec1f69bf8f540782df8fd371
WithdrawalsRoot:
0x15b6aa009007969019a7cc439a838e5feff3ff4a3277f3f768994eba79b9d5e9
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xfd485f511f909c5f2dd55bd46b1f9dbac183b88706b0000d784183806d9f6c1b
Parent Root Hash:
0x64cb7e7420d343179ed394d00d1d92d303e7c382089a2a48b54d25b889377291
Beacon Chain Deposit Count:
653012
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xdab9e48b1cf401c9be083a4b3d8fd5b238cadf7010ae6d31ebaf22e8da4f28af
Randao Reveal:
0xab73fc164dc52aa7cd6ebf26374e08ca51f00b6ab6f1d154503597cb64b2fd15f3f4e43016a5104365ebc502b30fe0ff119fd00744a2c80dd5ea4fb3110c69f92807a6c1637ea9f7c6f66ffe3bec1f7311ffda0edb98d3ba4bc416b19d57fa89
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.099430078383289268 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.