Block
#17133233
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1042 days ago (Apr-26-2023 10:01:11 PM +UTC)
Transactions:
174 transactions and 60 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.021848605169532469 ETH (0 + 0.483910315644879221 - 0.462061710475346752)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
90,728 bytes
Gas Used:
11,474,752 (38.25%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000040267686001 ETH (40.267686001 Gwei)
Burnt Fees:
🔥 0.462061710475346752 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,866.80 / ETH
Hash:
0x080451d720040689b187969ea853097c693730a60f6d1d55ddc9b78c6ca30d0f
StateRoot:
0x33961736737fb4fba3d613a19dbbf06abf42362aa099b375ea8bccae0bba5e7c
WithdrawalsRoot:
0xd9068b8026dd7e65657d22550de6c2ac8c9fea5e0a684c8f59884468b704bf38
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8299df488b0ab61901e0b9a7554f6fc9f5c9eb6d0a3c08c86d705e553565e43c
Parent Root Hash:
0x78997cc1b6ea6ce327086c1f6b9d1ed3b1d33f46fcb58c6e819099128999244c
Beacon Chain Deposit Count:
624489
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xad4f2943e0d6b20584fb0f31719c58645ca2e1a4de17683c0afffb76bedb902b
Randao Reveal:
0xb91d32ed33e2aa892fe07d85ab32ef19beeee4a94439fbdbbda75ad5564445bb0f59525538ebcd79d91fd1e52720b01208994080f1d86fca3838861bc9865ffd377de42c219b149bafa9f1618bad2a7f4c548d2285719bbd281d6a29a4b5131e
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.06297045556819784 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.