1---2name: tronscan-realtime-network3description: Query TRON real-time network data: latest block height, current TPS, node count, latest TVL, total transaction count, real-time vote count. Use when user asks "real-time TPS", "current block height", "node count", "TVL", "total tx count", or network status. Do NOT use for historical trends (use tronscan-data-insights); block details (use tronscan-block-info).4---56# Realtime Network Data78## Overview910| Tool | Function | Use Case |11|------|----------|----------|12| getLatestBlock | Latest solidified block | Solidified block height, hash, timestamp, witness, tx count |13| getCurrentTps | TPS & height | Current TPS, latest block height, historical max TPS |14| getHomepageData | Homepage summary | TPS, node count, chain overview, TVL, frozen |15| getNodeMap | Node map | Real-time node info and geographic distribution |16| getWitnessGeneralInfo | Witness aggregate | Total vote count, block stats, witness count |17| getTransactionStatistics | Tx statistics | Total tx count, token tx volume aggregates |1819## Use Cases20211. **Latest solidified block / confirmed block height**: Use `getLatestBlock` for solidified block (not chain-head latest); use `getCurrentTps` for latest block height.222. **Real-time TPS**: Use `getCurrentTps` for current TPS; use `getHomepageData` for overview TPS.233. **Real-time node count**: Use `getHomepageData` for node count; use `getNodeMap` for node list and distribution.244. **Latest TVL**: Use `getHomepageData` for latest TVL in homepage overview.255. **Total transaction count**: Use `getTransactionStatistics` for total tx count and token tx volume.266. **Real-time vote count**: Use `getWitnessGeneralInfo` for total vote count and witness stats.272829## MCP Server3031- **Prerequisite**: [TronScan MCP Guide](https://mcpdoc.tronscan.org)3233## Tools3435### getLatestBlock3637- **API**: `getLatestBlock` — Calls `/api/block/latest`; returns latest **solidified** block (number, hash, size, timestamp, witness, tx count). Note: Returns solidified block, not the chain-head latest block.38- **Use when**: User asks for "confirmed block", "solidified block height", or needs a stable block number. If user asks "latest block height" or "current block", clarify that the response is the solidified block and may lag behind the chain head.39- **Response**: number (block height), hash, size, timestamp, witness, tx count, etc.40- **Note**: Fields such as `witnessName`, `fee`, `energyUsage`, `blockReward`, `voteReward`, `confirmations`, `netUsage` may be 0 or null (underlying API does not return them)—ignore them. Use **tronscan-block-info** `getBlocks` when these fields are needed.4142### getCurrentTps4344- **API**: `getCurrentTps` — Get current TPS, latest block height, and historical max TPS45- **Use when**: User asks for "real-time TPS", "current TPS", "throughput", or "latest block height".46- **Response**: currentTps, latest block height, historical max TPS.4748### getHomepageData4950- **API**: `getHomepageData` — Get homepage data (TPS, node count, overview, frozen, TVL, etc.)51- **Use when**: User asks for "network overview", "node count", "TVL", or "homepage stats".52- **Response**: TPS, node count, chain overview, frozen resources, TVL, etc.5354### getNodeMap5556- **API**: `getNodeMap` — Get current node info and geographic distribution57- **Use when**: User asks for "node count", "node distribution", or "node map".58- **Response**: Current node info and geographic distribution.5960### getWitnessGeneralInfo6162- **API**: `getWitnessGeneralInfo` — Get witness aggregate stats (total votes, block stats, witness count)63- **Use when**: User asks for "real-time vote count", "total votes", or "witness stats".64- **Response**: Total vote count, block stats, witness count.6566### getTransactionStatistics6768- **API**: `getTransactionStatistics` — Get transaction statistics (total tx, token tx volume, etc.)69- **Use when**: User asks for "total transaction count" or "tx volume".70- **Response**: Total tx count, token tx volume, and other aggregates.7172## Troubleshooting7374- **MCP connection failed**: If you see "Connection refused", verify TronScan MCP is connected in Settings > Extensions.75- **API rate limit / 429**: TronScan API has call count and frequency limits when no API key is used. If you encounter rate limiting or 429 errors, go to [TronScan Developer API](https://tronscan.org/#/developer/api) to apply for an API key, then add it to your MCP configuration and retry.7677## Notes7879- For a single "real-time network" dashboard, prefer `getHomepageData` first (covers TPS, nodes, TVL); then add `getCurrentTps` for precise TPS/height, `getWitnessGeneralInfo` for votes, and `getTransactionStatistics` for total tx count.80- All tools are invoked via TronScan MCP `tools/call` with the tool name and required arguments.81- `getLatestBlock` may return 0/null for `witnessName`, `blockReward`, `voteReward`, `fee`, `energyUsage`, `netUsage`, `confirmations`; use **tronscan-block-info** `getBlocks` when these fields are needed.
dvcrn