Block
#17650712
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
964 days ago (Jul-08-2023 06:04:47 PM +UTC)
Transactions:
119 transactions and 49 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.156890710387472153 ETH (0 + 0.451245629677897857 - 0.294354919290425704)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
40,970 bytes
Gas Used:
16,817,467 (56.06%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000017502928312 ETH (17.502928312 Gwei)
Burnt Fees:
🔥 0.294354919290425704 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,865.62 / ETH
Hash:
0x5560f8eb170efa157317b687758d05ea441600d215c59a90eb87766d19676019
StateRoot:
0x351ad1a8da0871e535559cc4c952ebed97b1cea06ed26505edf78b10ed31ba63
WithdrawalsRoot:
0x1d31eb865500f1c95b081cc0f7bf591bf1b8c26de3c3d4a682e50af1cf7c15f0
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x23b1f1a1efa3a60c627e61315de06a07d637767f27815f8c27174d52264c55fe
Parent Root Hash:
0xfbd7afd1c721e3036328d8eb0214416d48e3dd6151b09359b4962d8ab6402e02
Beacon Chain Deposit Count:
844586
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x3a1c4edff4e82ee4a55dc0f82377213236ae7a5754d956676402842ed7ea14f7
Randao Reveal:
0x89be9b360c09f4ca8a188bc13e1386642e4bb76d173d5b13496c3171142be75a72e8fa045698c1e6b713edfb5cf0180b01c8aaec3870dc3ec574f5b003adb6c3e7677cc4487ada704f38d107733135d84bb657bfd47c71ba51e5053d65417299
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.157064991330165521 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.