Block
#20090130
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
646 days ago ()
Transactions:
157 transactions and 63 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.447007362663319508 ETH (0 + 0.568689224548601836 - 0.121681861885282328)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
71,431 bytes
Gas Used:
16,353,646 (54.51%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000007440656468 ETH (7.440656468 Gwei)
Burnt Fees:
🔥 0.121681861885282328 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,479.74 / ETH
Hash:
0x256be055334d9165702049161f08654a7974b002b2d38dbc2b2c65edc3fe6df2
StateRoot:
0x935c9fde37081b22bba782c5fc51f10c7f3994ee11f9d892db7a323f88f5d508
WithdrawalsRoot:
0xc87a39672bf78b9c26a3b082d03de0753e4ffaae91d74321a45d784acf52d19e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x802cf7a93c8c4c1a52da23b4e41db98f7044fc0c16a5b8e81bda1516be3cf354
Parent Root Hash:
0xd9e9925633af61325369d22bddaeb8105d22e6279223055d9fa90ca3c1a332db
Beacon Chain Deposit Count:
1536191
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x0b989d1b54076edae02fb693ed6cfbdffafc79ab28df952d79d6183538c3dcdc
Randao Reveal:
0x84e3e501f77f95c4af4dd98f1a52e3a0267bf3c23e9a079692476a03a794ac0441e45861d464fbbe77f40a945680807d037f2ec265e1c78a27b8c4c3ab2b75e3e7925ea0525b6da3c35297f6d8fe310191185800dcfbc5e3dae8c78a7ff94ade
Proposer Fee Recipient:
0xeBec795c9c8bBD61FFc14A6662944748F299cAcf (Fee Recipient: 0xeBe...Acf)
MEV Reward:
0.453046821772484581 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:
393,216 (3 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.