Block
#17320314
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
985 days ago (May-23-2023 06:58:59 AM +UTC)
Transactions:
228 transactions and 121 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.257843152736017307 ETH (0 + 1.254005525150863727 - 0.99616237241484642)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
274,742 bytes
Gas Used:
26,313,070 (87.71%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000037858082406 ETH (37.858082406 Gwei)
Burnt Fees:
🔥 0.99616237241484642 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,854.47 / ETH
Hash:
0x11a0848f35d3488698d4c109fac40651f926e7eb528f45fd124d3e385d9c7d48
StateRoot:
0xe1ee63d6ae0c1da4cd5e3283ed881ee04b5d11a733954b7f0e0e0be0b263b499
WithdrawalsRoot:
0x5f8743419fa42f1a1085ab1fb541b73e04513609b6d3a27b0f527f7953ac0240
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x4b4a1a1983733b3c2e4f93a3b0e84dede4321c44e93ad7be7a54bcd1c4fa6274
Parent Root Hash:
0xa334671b9284966059f850e84e4fe3a5a67fbdd66e0cc4f2fe5a77794c6b453c
Beacon Chain Deposit Count:
727887
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xe1f45564cebd4306a3c27acea949576cb5b7acf9155eb4950870c4386fdae94f
Randao Reveal:
0x96068ae3062183cc6f1f1fd6636d5b18d17e56365e024cfd6f4beda34bd3bb099f7c5193a7398724f5b98fdb4d0c7c6d09235f4d832375ce4e90d3f7a58edd5be30487968aae923f1a37a2da70e73bf7be8f486ebc1c2aa4f235411a7509eb77
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.238577679294203975 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.