🇺🇸English

TronScan Data Lookup Skill

Overview

This skill enables AI agents to query the TRON blockchain through the TronScan API. It provides eight Node.js scripts that cover all major data lookup operations: universal search, account details, transactions, token info, blocks, smart contracts, transfer history, and chain-level statistics.

All scripts output structured JSON to stdout and log progress to stderr, following the bankofai skill conventions.

Prerequisites

• Node.js >= 16
• npm (for installing dependencies)
• Run npm install in the skill root directory before first use

API Key

A TronScan API key is required. Set it as an environment variable before running any script:

export TRONSCAN_API_KEY="your-api-key-here"

Get a free key at https://tronscan.org/#/myaccount/apiKeys — scripts will exit with an error if the variable is not set.

Rate Limits

• Maximum 5 requests per second
• Maximum 100,000 total requests on the free-tier key
• All endpoints use HTTP GET (except contract event batch queries)
• Maximum limit per request is 200 (some endpoints allow up to 500)
• start + limit must be <= 10,000 for paginated endpoints

Usage Instructions

1. Universal Search

Search across addresses, tokens, contracts, transactions, and blocks.

node scripts/search.js <term> [--type <type>] [--limit <n>]

Parameters:

When to use: When you have a partial name, address, hash, or need to identify what something is on TRON.

2. Account Details

Look up account information, balances, token holdings, and resource usage.

node scripts/account.js <address>                          # Full account details
node scripts/account.js <address> --tokens [--limit <n>]   # Token holdings
node scripts/account.js <address> --wallet                 # Portfolio with USD values
node scripts/account.js <address> --resources              # Bandwidth & energy
node scripts/account.js <address> --analysis --type <0-4>  # Daily analytics

Modes:

When to use: When a user asks about a TRON wallet's balance, token holdings, staking resources, or account history.

3. Transaction Lookup

Retrieve individual transactions by hash or list transactions with filters.

node scripts/transaction.js <hash>                                  # By hash
node scripts/transaction.js --list [--from <addr>] [--to <addr>]    # Filtered list
node scripts/transaction.js --stats                                 # Network stats

List options:

When to use: When a user wants to look up a specific transaction hash, or query recent transactions for an address.

4. Token Information

Get token details, pricing, holder lists, supply data, and rankings.

node scripts/token.js --list [--filter <type>] [--sort <field>]   # Token rankings
node scripts/token.js --trc20 <contract_address>                  # TRC20 detail
node scripts/token.js --trc10 <token_id>                          # TRC10 detail
node scripts/token.js --price [symbol]                            # Current price
node scripts/token.js --holders <contract_address> [--limit <n>]  # Top holders
node scripts/token.js --supply <contract_address>                 # Total supply
node scripts/token.js --distribution <token_id>                   # Holdings distribution

List filters: trc10, trc20, trc721, trc1155, all, top Sort fields: priceInTrx, gain, volume24hInTrx, holderCount, marketcap

When to use: When a user asks about a specific token (price, holders, supply), or wants to browse top tokens on TRON.

5. Block Information

Query block details, recent blocks, or block statistics.

node scripts/block.js                                     # Latest block
node scripts/block.js <number>                            # By block number
node scripts/block.js --list --limit <n>                  # Recent blocks
node scripts/block.js --producer <address>                # By block producer
node scripts/block.js --stats                             # Network block stats

When to use: When a user wants to see the latest block, look up a specific block, or view block production statistics.

6. Smart Contract Details

Look up contract info, energy usage, call statistics, and caller analytics.

node scripts/contract.js <address>                         # Contract detail
node scripts/contract.js --list [--search <term>]          # Search/list contracts
node scripts/contract.js <address> --energy                # Energy consumption
node scripts/contract.js <address> --calls                 # Call statistics
node scripts/contract.js <address> --callers               # Caller list
node scripts/contract.js <address> --analysis --type <0-5> # Daily analytics

Analysis types: 0=callers, 1=calls, 2=energy, 3=bandwidth, 4=trx_transfers, 5=token_transfers

When to use: When a user asks about a smart contract's code verification status, usage, energy costs, or who is calling it.

7. Transfer History

Query TRX, TRC10, and TRC20 transfer history for addresses and contracts.

node scripts/transfer.js --trx <address>                             # TRX transfers
node scripts/transfer.js --trc20 <address> [--token <contract>]      # TRC20 transfers
node scripts/transfer.js --trc10 <address> [--token <token_id>]      # TRC10 transfers
node scripts/transfer.js --trc20-contract <contract> [--addr <addr>] # By contract
node scripts/transfer.js --internal <address>                        # Internal txns

Common options:

When to use: When a user wants to see transfer history for a wallet — incoming/outgoing TRX, USDT, or other tokens.

8. Chain Overview & Statistics

Get high-level TRON network data, super representatives, governance, and market data.

node scripts/overview.js                         # Full chain dashboard
node scripts/overview.js --tps                   # Current transactions per second
node scripts/overview.js --witnesses              # Super Representative list
node scripts/overview.js --params                 # Chain parameters
node scripts/overview.js --proposals              # Governance proposals
node scripts/overview.js --daily-accounts [days]  # New account growth
node scripts/overview.js --funds                  # TRX supply & burn data
node scripts/overview.js --trx-volume             # TRX price/volume history
node scripts/overview.js --nodes                  # Network node map

When to use: When a user asks about TRON network health, TPS, super representatives, governance, TRX supply, or market data.

Examples

Look up a TRON wallet and its USDT balance

# Get full account info
node scripts/account.js TDqSquXBgUCLYvYC4XZgrprLK589dkhSCf

# Get token holdings with USD values
node scripts/account.js TDqSquXBgUCLYvYC4XZgrprLK589dkhSCf --wallet

Check a transaction

node scripts/transaction.js 7f4a6d28e3c5f1b2a9d8e7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d9c8b7a6

Get the current TRX price

node scripts/token.js --price trx

List top 10 TRC20 tokens by market cap

node scripts/token.js --list --filter trc20 --sort marketcap --limit 10

Get recent USDT transfers for an address

node scripts/transfer.js --trc20 TDqSquXBgUCLYvYC4XZgrprLK589dkhSCf --token TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t --limit 10

Get chain overview

node scripts/overview.js

Error Handling

All scripts handle errors consistently:

Scripts exit with code 1 on error and output { "error": "message" } to stdout for machine parsing.

Security Considerations

• The API key is read-only — it cannot modify blockchain state
• The API key is loaded exclusively from the TRONSCAN_API_KEY environment variable and is never hardcoded
• Never embed private keys or wallet secrets in script invocations
• All queries are read-only GET requests against the public TronScan API
• The API key should be rotated if ever exposed in logs or public repositories
• Rate limit to 5 requests/second maximum to avoid key revocation

Common Token Addresses

The resources/common_tokens.json file contains well-known mainnet token addresses. Key tokens:

Agents can use these addresses directly instead of searching for them.

Version 1.0.0 — Created byM2M Agent Registry for Bank of AI

Weekly Installs

–

Repository

bofai/skills

GitHub Stars

1

First Seen

–

Security Audits

Gen Agent Trust HubPassSocketPassSnykWarn