Block
#18663893
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
818 days ago (Nov-27-2023 03:32:23 PM +UTC)
Transactions:
163 transactions and 68 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.074420869897440854 ETH (0 + 0.716062688776384334 - 0.64164181887894348)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
102,278 bytes
Gas Used:
14,997,177 (49.99%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000004278417324 ETH (42.78417324 Gwei)
Burnt Fees:
š„ 0.64164181887894348 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,027.67 / ETH
Hash:
0x6b49283398de3616501c1d30812af506794551fe26c37b5fdab1e4891355eed8
StateRoot:
0x48672b7075ef75cc33401dca5db8cd8f7fbfa6105ea8955f2110ac17c9b9cef1
WithdrawalsRoot:
0x080acf442f5231582f4f232f9f65b6859bbac9eeb7ddf59dd2e3841eb6b42d4f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x7c59f40126dba138dc7d5a109cad04b82fe688add715a49f2624e7e7cde96c19
Parent Root Hash:
0x07f101fec94ed115e3e3544023cd3893a3bf0ce2841a188d784397c0d75b829b
Beacon Chain Deposit Count:
1080242
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0x017853db8aaefb0bb3deda32950d3a57cece018d92816bfb7297f339761257e1
Randao Reveal:
0xa1782f3a3744943ae8116d646a5a23c1f393f22a52ab210da14d13f4aa8954aa416532922277d575031fa609f3f550a103e9e001a5775cda0a4f59a35200a75312b9c4149326a4647c32d63e11f3722bf288495c8a99f43f9191cf710263629b
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.07549714273314489 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.