Block
#16788030
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1338 days ago
Proposed On:
Block proposed on slot 5959093, epoch 186221
Transactions:
211 transactions and 106 contract internal transactions in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.101004172376802951 ETH (0 + 0.714746268042121171 - 0.61374209566531822)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
143,870 bytes
Transaction Actions: Beta
Gas Used:
22,688,849 (75.63%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000002705038478 ETH (27.05038478 Gwei)
Burnt Fees:
🔥 0.61374209566531822 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,437.65 / ETH
Hash:
0xe04455109eb2b79665a53329d4543c81d018dd603d1d113a9c36b9b0d8103c56
StateRoot:
0x066a9a0f7fbfe259b459d2915eb713494a34bb85ead7bdb34af118359e8fb019
Nonce:
0x0000000000000000
Slot:
5959093
Epoch:
186221
Proposer Index:
351949
Slot Root Hash:
0xa7633484af5a899779a4bbecccc164dd889f1ed1e834433c04b6b684652d863e
Parent Root Hash:
0x1ff34f63ffd986d10946326f8908f148d87162abd7b60260dcbce3e036e6d584
Beacon Chain Deposit Count:
561571
Slot Graffiti:
🍀🍀溟深辰远🍀🍀 (Hex:0xf09f8d80f09f8d80e6ba9fe6b7b1e8beb0e8bf9cf09f8d80f09f8d8000000000)
Block Randomness:
0x6b5f598c9b2d977e95a3b5cc137b6e852349f9f7d360d991ead598a83474a88c
Randao Reveal:
0xa55b13643a052a42f48ba9533beeb62c2b063891fd6709d7d70e2b37348cacef0414a2e892a4feb10ebe5946faab91d611d7597c80ee8d06d3f4b2b30396ecaf506ff365f50b445838b6b533a8cee098e71bc16de44fd26ca7e271d2605cfa32
Proposer Fee Recipient:
0xA8C62111e4652b07110A0FC81816303c42632f64 (Fee Recipient: 0xA8C...f64)
MEV Reward:
0.153590487017125361 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:
| Rank | Participants | Txn Count | % Gas Used | Txn Fee (USD) |
|---|
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.