‹ 首页

tronscan-data-lookup

@bofai · 收录于 5 天前 · 上游提交 1 周前

Query TRON blockchain data via the TronScan API — accounts, transactions, tokens, blocks, contracts, transfers, and chain statistics.

适合你,如果你需要从 TRON 区块链获取结构化数据用于开发或分析。

/ 通过 npx 安装 校验哈希
npx oh-my-skill add bofai/skills/tronscan-data-lookup
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- bofai/skills/tronscan-data-lookup
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify bofai/skills/tronscan-data-lookup
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
88GitHub stars
~2.3K最小装载
~7K含声明引用
~9.2K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 39919d1 · 表述以原文为准
它做什么

装上后,Claude能查询TRON区块链的账户、交易、代币、区块、合约、转账和链统计等数据。

什么时候触发

当用户询问TRON钱包余额、交易记录、代币信息或链上统计时触发。

装好后可以这样说
会查询账户详情和代币持有。
会查询转账历史。
会返回链概览统计。
技能原文 SKILL.md作者撰写 · MIT · 39919d1

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 (Optional)

If no API key is configured, scripts automatically use the BofAI proxy (ts.bankofai.io) — no setup needed.

To use your own TronScan API key instead (higher rate limits), set the environment variable:

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

Get a free key at https://tronscan.org/#/myaccount/apiKeys

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: | Param | Description | Values | |-------|-------------|--------| | term | Search query (positional, required) | Any string | | --type | Filter result type | token, address, contract, transaction, block | | --limit | Max results | 1–50, default 20 |

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: | Flag | Description | |------|-------------| | (none) | Full account detail (balance, creation date, permissions, witness status) | | --tokens | All token balances. Use --show 1 for TRC20 only, 2 for TRC721, 3 for all, 4 for TRC1155 | | --wallet | Portfolio view with USD-denominated values | | --resources | Bandwidth/energy allocation (Stake 2.0) | | --analysis | Daily analytics. --type: 0=balance, 1=transfers, 2=energy, 3=bandwidth, 4=transactions |

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: | Param | Description | |-------|-------------| | --from | Filter by sender address | | --to | Filter by receiver address | | --block | Filter by block number | | --start_timestamp | Start time (ms) | | --end_timestamp | End time (ms) | | --sort | Sort field (default: -timestamp) | | --limit | Results per page (default 20, max 200) | | --start | Pagination offset |

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: | Param | Description | |-------|-------------| | --direction | 0=all, 1=incoming, 2=outgoing | | --start_timestamp | Start time (ms) | | --end_timestamp | End time (ms) | | --limit | Results per page (default 20, max 200) |

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:

| Error | Cause | Solution | |-------|-------|----------| | Missing required argument | Required positional arg not provided | Check usage in script header | | Request failed with status 403 | API key invalid or rate limited | Check TRONSCAN_API_KEY, reduce request frequency | | Request failed with status 404 | Endpoint not found or invalid params | Verify address/hash format | | timeout of 15000ms exceeded | API server slow or unreachable | Retry after a few seconds | | ENOTFOUND | No network connectivity | Check internet connection |

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
  • When no API key is set, requests go through the BofAI proxy (ts.bankofai.io) with no key header
  • 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:

| Symbol | Contract Address | Decimals | |--------|-----------------|----------| | TRX | (native) | 6 | | USDT | TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t | 6 | | USDC | TEkxiTehnzSmSe2XqrBj4w32RUN966rdz8 | 6 | | USDD | TPYmHEhy5n8TCEfYGqW2rPxsghSfzghPDn | 18 | | WTRX | TNUC9Qb1rRpS5CbWLmNMxXBjyFoydXjWFR | 6 | | BTT | TAFjULxiVgT4qWk6UZwjqwZXTSaGaqnVp4 | 18 | | JST | TCFLL5dx5ZJdKnWuesXxi1VPwjLVmWZZy9 | 18 | | SUN | TSSMHYeV2uE9qYH95DqyoCuNCzEL1NvU3S | 18 |

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


Version 1.0.0 — Created by M2M Agent Registry for Bank of AI

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。