Block
#17582178
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
973 days ago (Jun-29-2023 03:06:59 AM +UTC)
Transactions:
127 transactions and 71 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.199453895363215227 ETH (0 + 0.426187075668579736 - 0.226733180305364509)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
58,897 bytes
Gas Used:
12,522,349 (41.74%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000018106281841 ETH (18.106281841 Gwei)
Burnt Fees:
🔥 0.226733180305364509 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,851.93 / ETH
Hash:
0x30cfcd92e94e007884b7c89257e3d9b3452c7fd80c446d1d4531569fb1209f93
StateRoot:
0x41fc0db64420bd5c0ff310b97da830cb7998d2b87ce26ffe09fced87d067b527
WithdrawalsRoot:
0x64a39d1649405e7d9c68cd3f975f5e02be9533271c181e5d2647d70ca07ae5d5
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x3554fde31311c078a1ffdfd3aa5a3c994ee1ae0297edc2351af29b21d213e0f6
Parent Root Hash:
0xfd24c764a5f899583a51d1b756c5960f99be5d55aa0f7b3ead1c72cd495bdda4
Beacon Chain Deposit Count:
831007
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x53a9af577b8164ed2730119ca97e04e3d3e2af1bc0a12a1e5338c1e6c6204fab
Randao Reveal:
0xa8f6020ac94258a4a25318e2cf5686e03a7e8e6c07c1b6d3660b9fdd2c6b6155d41f7c9d5fa40218665d460971694d740621198a14a6a14ea85988ae52d59995584088cf81460eaea8c462905e7c1ab28d89865af80a2ca8d31ea16736897cef
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.201833292350460946 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.