Block
#20061121
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
645 days ago ()
Transactions:
182 transactions and 59 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.069464137469599841 ETH (0 + 0.13101639535308875 - 0.061552257883488909)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
63,756 bytes
Gas Used:
14,140,369 (47.13%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004352945661 ETH (4.352945661 Gwei)
Burnt Fees:
🔥 0.061552257883488909 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,665.99 / ETH
Hash:
0x326c892ddf6b95174753f5202bbc2f9d3854f7188f9c539c5c7993b3282ae637
StateRoot:
0x4f09b25492270294b7939896d79c72d85143f41d838b66153836425e52dc45e9
WithdrawalsRoot:
0x37b77e450756e2111a6022f1659d34b27910ea74470cd8099af37b071a037a07
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x8ab8337f7fd1c1969b886e729934051f282c0fbf2e3193318689f5a64fc01958
Parent Root Hash:
0x903dd88482e61e044205f7d214e1a7fb700324ba0f839b6bf2a98820cd2866a6
Beacon Chain Deposit Count:
1527109
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x82aa2b2e26aeaf173c0956cb481353f9c8c0b4c6257bc3a9159ff4d94d5d4b2e
Randao Reveal:
0xa9c7f2e90e8d4dae2570915cc533d4456cff12c601014e4d43689e4343bde983d580d64e83832bb5f2b484fc749f9f4107a4388b418ddb061a5fca6c74ef770477d48bbfd6063cb692c60fd6514c5460b3b65a63d779b8b3c803138950506ad1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.0696963725324039 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
0 (0 blobs)
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.