trongrid-block-info

Query and analyze TRON blocks including producer info, transaction breakdown, rewards, burns, and network load. Use when a user asks about a specific block, latest block, block height, block rewards, block producer, transaction count, or network status. Supports single block lookup, block ranges, confirmed blocks, and multi-block trend analysis.

Audits

Pass

Install

openclaw skills install trongrid-block-info

Block Info

Query and analyze TRON blocks — latest block data, block rewards, producer info, TRX burns, resource consumption, transaction breakdown, and network load trends.

MCP Server

Instructions

Step 1: Fetch Block Data

Choose the right tool based on the query:

Query TypeToolParameters
Latest blockgetBlocknone (omit id_or_num)
Latest confirmed blocksolidityGetBlocknone (omit id_or_num)
Block by numbergetBlockid_or_num=<height>, detail=false
Block rangeloop getBlockid_or_num=<height> incrementing, detail=false
Latest N blocksloop getBlock N timesstart from latest, decrement id_or_num
Block statisticsgetBlockStatisticsblockNum

Step 2: Parse Block Header

Extract from the block response:

  • Block Number (height), Block Hash, Timestamp
  • Parent Hash (link to previous block)
  • Witness Address (producer SR)
  • Version number

Step 3: Identify Block Producer

  1. Extract witness address from block header
  2. Call getPaginatedNowWitnessList to match address to SR name/URL
  3. Call getBrokerage for the producing SR to get reward distribution ratio

Step 4: Analyze Block Transactions

  1. Count and categorize transactions from block data: TRX transfers, TRC-10 transfers, smart contract calls, contract deployments, staking, voting, other
  2. Call getTransactionInfoByBlockNum for receipts — reveals total fees, energy consumed, bandwidth consumed, success/failure counts

Step 5: Calculate Rewards & Burns

From transaction receipts:

  • Block Reward: 16 TRX per block (current parameter)
  • TRX Burned: Sum of energy/bandwidth/account creation fees burned
  • SR Revenue: Block reward + allocated transaction fees

Step 6: Assess Network Load

Compare block metrics against capacity:

  • Transaction density vs. block capacity
  • Energy/bandwidth utilization rates
  • For trends, loop getBlock 10–20 times (decrementing id_or_num) and compare

Step 7: Check Block Events

Call getEventsByBlockNumber for smart contract events (DeFi swaps, token transfers, governance actions).

Step 8: Compile Block Report

## Block #[number]

### Overview
- Hash: [hash]
- Time: [timestamp]
- Producer: [SR name] ([address])
- Brokerage: [X%]

### Transactions
- Total: [count] (Success: [X], Failed: [Y])

| Type | Count | % |
|------|-------|---|
| TRX Transfer | XX | XX% |
| Contract Call | XX | XX% |
| Staking | XX | XX% |

### Economics
- Block Reward: [X] TRX
- Fees: [X] TRX | Burned: [X] TRX

### Resources
- Energy Used: [amount]
- Bandwidth Used: [amount]
- Network Load: [Low/Medium/High]

For multi-block trend queries:

## Network Status (Last [N] Blocks)
- Avg Transactions/Block: [count]
- Avg Block Time: [X.X]s
- Total TRX Burned: [amount]
- Current Height: #[number]
- Load Trend: [Increasing/Stable/Decreasing]

Error Handling

ErrorCauseResolution
Block not foundFuture block number or invalid hashCheck current height with getBlock (no params) first
Empty blockBlock with zero transactionsReport as empty block — this is normal for low-activity periods
Range too largeLooping getBlock for many blocksSplit into smaller batches; avoid requesting more than 100 blocks in a single flow
No eventsBlock has no smart contract activitySkip events section, note "No contract events in this block"

Examples