Practical overview
When it fits
Use it when you need a read-only first look at a TRON address, approval, contract, transaction or URL, or when you want to run the inspection interface locally.
Who it is for
- TRON users checking an address or link before using it in a wallet
- Security researchers reviewing on-chain signals and readable source
- Developers seeking to run or adapt the JavaScript app and its worker proxy
- Compliance and OSINT practitioners examining AML-style signals and counterparty exposure
Documented uses
- Review an address's risk score, token holdings, activity and approvals.
- Check AML-style categories and counterparty exposure.
- Find active or unlimited TRC-20 allowances and inspect account permissions.
- Review contract privilege and proxy patterns or decode transaction data.
- Screen a URL for typosquatting, homoglyphs and TRON-themed lures.
Requirements & limits
The project identifies a hosted browser app and a public MIT-licensed repository. Its README says address and URL inspection can be done without creating an account or connecting a wallet.
- The app is read-only and does not execute transactions.
- Hosted and recommended self-hosted API requests use a Cloudflare Worker proxy; self-hosting requires configuring a worker, secrets, proxy URL and CORS.
- The vanity generator searches locally in Web Workers, while other inspection modules use external data services through the proxy.
- The interface is built with vanilla JavaScript and lists eight UI locales.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Run the app locally with a static server
Open the repository's app shell from a local static web server.
Before you start
- A clone of the Tronsec repository
- Python, for its built-in HTTP server
Steps
Clone the repository and change into its directory.
Run the command below.
python -m http.server 8080Open
http://localhost:8080/app/in a browser.
Expected outcome
The app shell is served locally at the documented address.
Guide limitations
- This setup guide does not configure a custom API proxy or credentials.
- The README describes local direct API keys as an optional advanced-development setup.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- jamejohns/tronsec · Official homepage title · retained in its source language

