Block
#17961663
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
923 days ago (Aug-21-2023 07:38:23 AM +UTC)
Transactions:
130 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.318620227679972558 ETH (0 + 0.488719389283725093 - 0.170099161603752535)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
139,461 bytes
Gas Used:
14,044,415 (46.81%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012111516329 ETH (12.111516329 Gwei)
Burnt Fees:
🔥 0.170099161603752535 ETH
Extra Data:
@builder0x69 (Hex:0x406275696c64657230783639)
Ether Price:
$1,667.27 / ETH
Hash:
0xde3fdf68b949ad19b60e7f87e804f68a9b6d853b3d069a8476337056e0aa22eb
StateRoot:
0xfa22e702b1671a43c7e04c1e7d0aad13ac868c6d525f369ff4332b3de4d086da
WithdrawalsRoot:
0x906471839b799bebae39eb2abbe1bb9a138b203aa6bb098c8ebd2338c8465f94
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf4a5ab6b619bc5986b92ae15231679c2d203565788f2c972df322d61a2fab503
Parent Root Hash:
0xb8b445f0547b79672623592bea6c17baaebc11c78d803bd617f3a5353d77c451
Beacon Chain Deposit Count:
919771
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xb82229ce51b3d9ab218d7ead59f2f6392e77260eb04db71b88748813d78e43ad
Randao Reveal:
0xa889b0852622eaa1d68afc6edaee5e08421b71ce2c6dca86810fef6891dd1a529a172b5a740dd2324a9bc4ba8f592bb3167b46dbecfb036cff9de431f5b271cc5501f5dc20d5cd14f6d7dbdbdba345cbb6e817f5cfe83d70c02e07149bc925b4
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.32102696814279722 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.