# 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.

- Skill: `dvcrn/trongrid-block-info` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add dvcrn/trongrid-block-info`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dvcrn/trongrid-block-info/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dvcrn (https://skillmd.com/u/dvcrn)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/dvcrn/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
- **Prerequisite**: [TronGrid MCP Guide](https://developers.tron.network/reference/mcp-api)

## Instructions

### Step 1: Fetch Block Data

Choose the right tool based on the query:

| Query Type | Tool | Parameters |
|-----------|------|------------|
| Latest block | `getNowBlock` | none |
| Latest confirmed block | `solidityGetNowBlock` | none |
| Block by number | `getBlockByNum` | `num` |
| Block by hash | `getBlockById` | `value` |
| Block range | `getBlockByLimitNext` | `startNum`, `endNum` |
| Latest N blocks | `getBlockByLatestNum` | `num` |
| Block statistics | `getBlockStatistics` | `blockNum` |

### 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 `listWitnesses` 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
3. Optionally call `getBlockBalance` for all balance-changing operations

### 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, fetch 10-20 recent blocks with `getBlockByLatestNum` 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

| Error | Cause | Resolution |
|-------|-------|------------|
| Block not found | Future block number or invalid hash | Check current height with `getNowBlock` first |
| Empty block | Block with zero transactions | Report as empty block — this is normal for low-activity periods |
| Range too large | `getBlockByLimitNext` with >100 block spread | Split into smaller ranges (max 100 per call) |
| No events | Block has no smart contract activity | Skip events section, note "No contract events in this block" |

## Examples

- [Get latest block details](examples/latest-block-details.md)
- [Analyze block rewards](examples/block-reward-analysis.md)