Block
#20090815
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
649 days ago ()
Transactions:
224 transactions and 124 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.054898418687254741 ETH (0 + 0.419976393443529707 - 0.365077974756274966)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
92,789 bytes
Gas Used:
19,465,262 (64.88%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000018755358893 ETH (18.755358893 Gwei)
Burnt Fees:
🔥 0.365077974756274966 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,479.74 / ETH
Hash:
0x59a1d3b2b44d74ac4e71dad5cbf9152a2f04a5f328d61641c3663366727a3da8
StateRoot:
0x713783ff4c9237941aee91571d937cdd702b4c8195a27ec321fe325e9d802686
WithdrawalsRoot:
0x7dbbc2f527813224f7e1ab90839ba160305d1a19f7e97c83bf6e5150d2d10058
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc976f029a8574b0eacf4fc963750259c846b143629d75d5b1fa98f09c51d2d45
Parent Root Hash:
0x44f29c8ed22256cce27f877c8043190e7107028f6596ebab3b2f6005ece0c616
Beacon Chain Deposit Count:
1536856
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x1191e355368ba65cb83094661ec54acac38eeb418ec296edf5ae1f7b3a6c88b6
Randao Reveal:
0x95e5f5cf51bc1b48698daeaa7f232762dda76ff472c04d6b629b221a8d440ce155f471d43eef5fdfed065488bd1c138607896f7ee805d8594d001dc4a7a4f12ff6a914f93d62b2aa6cdf8ebd1bf6eb19ef8502d427385bf9017d802fa23068b8
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.049676638614860538 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
2 wei (0.000000002 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000001572864 ETH
Excess Blob Gas:
3,014,656 (23 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.