Block
#17310526
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1008 days ago (May-21-2023 09:54:47 PM +UTC)
Transactions:
112 transactions and 67 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.496595503006305393 ETH (0 + 0.844651733219371279 - 0.348056230213065886)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
46,120 bytes
Gas Used:
11,873,942 (39.58%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000029312609933 ETH (29.312609933 Gwei)
Burnt Fees:
š„ 0.348056230213065886 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,805.42 / ETH
Hash:
0x25d812c1714ff28e6142eae0b264042047802e81c6ac25b32ae2724f2e7c0b4f
StateRoot:
0xa6a6fafe9a87c2a597a6ff2d7917f332949533b22f843efba170bbe74c5caa01
WithdrawalsRoot:
0x91de9da12b7e87d4613c227ea9c81b6ca5b1060cff83a4c77440aab53fb01b5b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x907ad0ba6b269a20efae1d8124df45ce85aadbbdb47fbd31a9e4de6a346a7828
Parent Root Hash:
0xde700cd13a8085c1a84f8c00ea2ab685c259083963c346fe3df1e5b057912523
Beacon Chain Deposit Count:
724419
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x07a2eea04500f9c776a55b444987859f460471be7f4b18d81d47ebdbd66a7ead
Randao Reveal:
0xa3ffe890566943b6a24ff0c0075ae597567a59bceaa149cc8ca63dd58670a2badee8adcdffd9eefa8576bca72670fa2e19a198f0ea3e3a6098f14178fbaebcaf16a20cd7a4eab11c5b21b32df06ca36897e7055746e319c3e3fd132136132b64
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.493801841962390101 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.