Block
#17679906
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
956 days ago (Jul-12-2023 08:39:35 PM +UTC)
Transactions:
141 transactions and 70 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.064309139303395979 ETH (0 + 0.365810916494423469 - 0.30150177719102749)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
68,521 bytes
Gas Used:
13,956,965 (46.52%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000021602244986 ETH (21.602244986 Gwei)
Burnt Fees:
š„ 0.30150177719102749 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,871.86 / ETH
Hash:
0xd899396cda4c195bd0142242b36e1126f7695dd61d9907538eb9b104d8f6a822
StateRoot:
0xd3ba2b058973959d18b08f8df466ab17a7c78892599468ef240f662c882e78df
WithdrawalsRoot:
0x5dc38f52060ae2e5d55c30689f26e3f5115e95f53be7bdd25aa98efef36c5ce3
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x9f2859e5f946c5c142958123fa2c1731c96ae77897e0377f7787d90c08fa5f31
Parent Root Hash:
0x414464e4dc166c389fcb51a1bb780aeddcb299d5fcfe944ab724a635624249ad
Beacon Chain Deposit Count:
849271
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xb219b2bf70ab0fb495c7ea11c51630a2305988830c079cbdff7e9446bfd8e134
Randao Reveal:
0x8758e2b787441cf117ea2674904815f95f9478913e0f50b442d9af191d25c609613f850bc56a1765c1e630a71b6f8f2e10b5fcaee82d8deb1819b8f728def392ed922fb8dbb74e2ac4b30ace7bb948a2dc6e4edef2c2729441ca8234c6dd3c61
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.064181492064510533 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.