Block
#16648367
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
1360 days ago
Proposed On:
Block proposed on slot 5817675, epoch 181802
Transactions:
141 transactions and 68 contract internal transactions in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.169603827297766441 ETH (0 + 0.429416284260434765 - 0.259812456962668324)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
63,559 bytes
Transaction Actions: Beta
Gas Used:
12,050,467 (40.17%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000021560364172 ETH (21.560364172 Gwei)
Burnt Fees:
🔥 0.259812456962668324 ETH
Extra Data:
by @builder0x69 (Hex:0x627920406275696c64657230783639)
Ether Price:
$1,694.30 / ETH
Hash:
0xa35ab99b9998610ec255e21c855e4acb26fd894d1d104048e510f7532327881b
StateRoot:
0xedd030408ce370fd1d0d59dbbf3ddbac6d190ae48047810702aa709f960f6b3d
Nonce:
0x0000000000000000
Slot:
5817675
Epoch:
181802
Proposer Index:
79017
Slot Root Hash:
0x3f5ebaa5eaadae230645dbf0423306173507e65cad38c60edd91d19f8f2022b0
Parent Root Hash:
0xbc3620e17da854e1bde1f1aebf2760accc97d95c576555e7ae3d01e9cfb77130
Beacon Chain Deposit Count:
534371
Slot Graffiti:
🍀🍀溟深辰远🍀🍀 (Hex:0xf09f8d80f09f8d80e6ba9fe6b7b1e8beb0e8bf9cf09f8d80f09f8d8000000000)
Block Randomness:
0xbf9d8d62ffe256a8a03853686a918623e57c3b2d099c24da9cf3f67792ba4cd3
Randao Reveal:
0xaffd48bc06bb1ce9fab1f9c3da6cfd298959c6453b58f2aae4416a289210a954850ca9a3348680f78613615e1e96df3602f4d594f9a8986ea948d5f57c66e2b41b86cb312d3ac2cde9420af6b21a30ff4323ca6c525595da8884151af18a79c2
Proposer Fee Recipient:
0x535B918F3724001FD6Fb52fCC6cBC220592990A3 (Fee Recipient: 0x535...0A3)
MEV Reward:
0.169810917283036441 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.