dvcrn Contract Analysis
Overview
| Tool | Function | Use Case |
|---|---|---|
| getContractDetail | Contract info | Balance, verification, call count, method map |
| getContractCallStatistic | Call stats | Call count, top callers, top methods |
| getContractCallers | Caller list | Callers and call count for a given day |
| getContractEvents | Events | Transfer events and method calls |
| getContractList | Contract list | Search by name/address, sort, paginate |
| getContractEnergyStatistic | Energy usage | Total and daily energy consumption |
| getContractTriggerTransactions | Trigger txs | Contract-triggered transactions in time range |
| getContractAnalysis | Daily analysis | Balance, transfers, energy, bandwidth, calls, fee |
Use Cases
- Deploy & Basic Info: Use
getContractDetailfor balance, verification status, call count, method mapping. - Hot Methods: Use
getContractCallStatisticfor top called methods. - Top Callers: Use
getContractCallStatisticorgetContractCallersfor top 5 or full caller list. - Open-source / Verification: Verification status is in
getContractDetail. - Transaction Count: Use
getContractDetailorgetContractTriggerTransactionsfor call/tx volume. - Malicious Clues: Combine events (
getContractEvents), energy (getContractEnergyStatistic), and call stats to spot unusual patterns.
MCP Server
- Prerequisite: TronScan MCP Guide
Tools
getContractDetail
- API:
getContractDetail— Get contract details (balance, verification status, call count, method map) - Use when: User asks for "contract info", "contract address", or "is contract verified".
- Input: Contract address.
- Response: Balance, verified flag, call count, method map.
getContractCallStatistic
- API:
getContractCallStatistic— Get contract call stats (call count, top callers, top methods) - Use when: User asks for "hot methods", "top callers", or "who calls this contract".
- Input: Contract address (and optional time range).
- Response: Call counts, top callers, top methods.
getContractCallers
- API:
getContractCallers— Get all callers and call count for a given day - Use when: User asks for "caller list" or "who called today".
- Input: Contract address, date.
getContractEvents
- API:
getContractEvents— Get contract events (transfer events and method calls) - Use when: User asks for "contract events" or "transfers from contract".
- Input: Contract address, pagination.
getContractList
- API:
getContractList— Get contract list with search by name/address, sort, pagination - Use when: User searches contracts by keyword or browses list.
getContractEnergyStatistic
- API:
getContractEnergyStatistic— Get contract energy consumption (total and daily) - Use when: User asks for "contract energy" or "gas usage".
getContractTriggerTransactions
- API:
getContractTriggerTransactions— Get contract-triggered transactions in a time range - Use when: User asks for "contract transactions" or "recent calls".
getContractAnalysis
- API:
getContractAnalysis— Get contract daily analysis (balance, transfers, energy, bandwidth, calls, fee) - Use when: User asks for "contract activity over time".
Troubleshooting
- MCP connection failed: If you see "Connection refused", verify TronScan MCP is connected in Settings > Extensions.
- 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 to apply for an API key, then add it to your MCP configuration and retry.
Invalid contract address
Ensure the address is a valid TRON contract (not an EOA address). Use TRC20/721/1155 contract address for token contracts.
Notes
- To assess malicious risk: check verification, top methods (unusual names), energy spike, and event patterns.
- Top 5 callers and top methods come from
getContractCallStatistic.