How to Find & Verify Your Token on Tronscan
Make your contract readable and trustworthy on TRON’s block explorer.
Updated
Tronscan is TRON’s main block explorer - the public record where anyone can look up your token, see its supply, holders and transactions, and read its contract. Making your token easy to find and verify on Tronscan is a basic trust signal every serious project should tick off.
Finding your token on Tronscan
- Go to tronscan.org.
- Paste your token’s contract address (the
T…address from when you created it) into the search bar. - You’ll land on the token page, showing its name, symbol, total supply, holder count and transfer history.
Bookmark this page and share it - it’s the canonical place for people to confirm your token is real.
What “verifying the contract” means
By default, a deployed contract is stored on-chain as compiled bytecode, which isn’t human-readable. Verifying means publishing the original source code and compiler settings so Tronscan can confirm they match the bytecode. Once verified, anyone can read your contract’s code directly on Tronscan - a strong transparency signal.
How verification works
Contract verification is done through Tronscan’s “Verify Contract” tool, where you submit the source code, the exact compiler version, and any settings used at deployment. Tronscan recompiles and checks it matches the on-chain bytecode. Because our tokens are built from a standard, audited TRC-20 template, the source is consistent and well-understood - contact us if you need the verification details for your deployment.
The verification steps
If you’re verifying a contract yourself, the flow on Tronscan is broadly:
- Open your token’s contract page on Tronscan and find the Contract tab, then Verify and Publish.
- Enter the contract name and select the exact compiler version used at deployment.
- Choose the right optimization setting (on/off and the runs value) - it must match what was used to compile.
- Paste the complete source code (including any imported files, or a flattened single file).
- Submit. Tronscan recompiles and, if the bytecode matches, marks the contract verified with a green tick.
The single most common reason verification fails is a mismatched compiler version or optimization setting - they must be identical to deployment. Because our tokens use a consistent standard template, those details are known; contact us for the exact settings for your deployment.
What to check on your token page
- Total supply matches what you intended.
- Holders - the creator wallet should hold the supply right after launch, then your liquidity pool once you add it.
- Owner / functions - confirm whether ownership is active or renounced.
- Transfers - activity looks as expected.
Frequently asked questions
Is my token on Tronscan automatically?
Yes - every on-chain token appears on Tronscan as soon as it’s deployed. Verification of the source code is an extra, optional step.
Do I have to verify the contract?
It’s not required for the token to work, but it’s strongly recommended for trust, especially before a DEX listing.
Where do I get the contract address?
From your token’s success screen when you create it, or from your wallet’s token details.
Why did my verification fail?
Almost always a mismatch in compiler version or optimization settings versus what was used at deployment, or missing imported source files. Match those exactly and it will pass.
Does verifying cost anything?
Verification itself is free on Tronscan - it’s a source-code submission, not an on-chain transaction. You only ever pay normal network fees for actual on-chain actions.
Can I verify a token made with your tool?
Yes. Our tokens are built from a standard, audited TRC-20 template, so the source and settings are consistent - contact us for the verification details for your specific deployment.