Block
#20476769
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
587 days ago ()
Transactions:
119 transactions and 43 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x88c...34A in 12 secs
Block Reward:
0.073374503286384301 ETH (0 + 0.120754161870597251 - 0.04737965858421295)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
48,620 bytes
Gas Used:
11,274,650 (37.58%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004202317463 ETH (4.202317463 Gwei)
Burnt Fees:
🔥 0.04737965858421295 ETH
Extra Data:
jetbldr.xyz (Hex:0x6a6574626c64722e78797a)
Ether Price:
$2,343.50 / ETH
Hash:
0xfc10633c9d2dd6ebe8f9a67ea950201563488c966f1f64595081bbf0d7eb47f2
StateRoot:
0xf6b1a8cd43452b48ef0e538b48ad2fa2c3add08ea9d5aa88b561a8e38f2a548a
WithdrawalsRoot:
0x118911ba7861e51827b345565b1ad71cbfd5314e9590d5173071d27d55c10d04
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5a8a7c7824933d44ad7c98f1f7baf61a3fffb9762760926754fbfd7c320c51bc
Parent Root Hash:
0xbc9fc0a5088f720ba5b34c02eb3c3dbd73bcee324a100bba409bcda33d9a6eb1
Beacon Chain Deposit Count:
1629225
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xdeebd603f1d14b6371b95f5d3831b2b9e9f63f1488b6ae29cc17e7f270efb11a
Randao Reveal:
0xae64875bef9b960d6f247d7ab057f1037380b4bd48ecd9ff1167b6685462fe5ef0cbd1a64d2af85e85db643879762eac06a1a7767cfd5369de68dad054dd2c69a45124f1159ff6775887a5243641e1389e9a642ef095fa8eb740ce8444989ff1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.077120259630698467 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
4 wei (0.000000004 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000003145728 ETH
Excess Blob Gas:
5,111,808 (39 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.