Block
#18738668
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
820 days ago (Dec-08-2023 02:49:47 AM +UTC)
Transactions:
133 transactions and 64 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.13473002170404427 ETH (0 + 0.630764910382927859 - 0.496034888678883589)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
85,029 bytes
Gas Used:
11,725,289 (39.08%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000042304704701 ETH (42.304704701 Gwei)
Burnt Fees:
🔥 0.496034888678883589 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$2,358.94 / ETH
Hash:
0x2639094683cd79b7583780d5085f0d4e6a48a51fa6853e1cb53c357be3ccc319
StateRoot:
0x3d53bb7fab08cd002772ee3e89071f30b4376d5605733c4e8654d6ef24ea059a
WithdrawalsRoot:
0x12c4fbd36293ede5a6477e2cf5fc0d37aa18e33159069a6a44f072ae56018d1c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc87c4285e82955b1484b2edc17c902ec91f8602b518369c7e7344146b45fa62e
Parent Root Hash:
0x3dc592337c2ea9112f252e87008ca150e2c41c6fff0ae5c83ec8fe6299cbcee1
Beacon Chain Deposit Count:
1103703
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xdcbd7bce4e49b88d84792d9edbf9fdd75d13e6ec52572ac55d7abd27dcf068c7
Randao Reveal:
0x91af4ae64543c6510bc970c2c220bbb68a76da8ac52102cd1246a885aab61d487e01e9af47cf02435dca5ef4a4fe0db70053dae9900ffcc9339ae207303b036f1d71114de3ccc464bb235428effc910cfb393689878134cb015da8433763dc3e
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.113678295383659456 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.