On-chain security analysis — is it a scam or legit?
BNB ChainThe RT contract is a standard ERC-20 token implementation utilizing OpenZeppelin libraries.
Read the full analysisEach factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
Holder balances as recorded by the audit of Nov 1, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0x6cee…9d29No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 1 address(es) other than the owner/deployer. One of them — a wallet, 0x6cee…9d29 — holds 100.0% and can remove that share at once; who controls it is not visible on-chain, so it is not treated as an independent provider. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (mint capability, holder concentration) were applied separately and feed the risk score.
Re-check after any contract upgrade or ownership change, both of which can alter behaviour without changing this page.
Acknowledged
The ten largest holders own 100.0% of supply. What remains: 99.9% in wallets, 0.0% in other contracts. 11,734 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
Listed on CoinGecko as RealGo (RT). 11,734 holders.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $23K (DexScreener, all pools). 24h trading volume $3.4M (CoinGecko, all markets, daily snapshot). 24h trading volume $127K (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: fixed — the contract has no mint function. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $23K of DEX liquidity across 1 pools. Launch: 10 days of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The token's oldest DEX pool is 10 days old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
The RT contract is a standard ERC-20 token implementation utilizing OpenZeppelin libraries. It includes EIP-2612 permit functionality and burnable capabilities. No privileged roles or administrative backdoors were identified in the source code.
The architecture follows standard OpenZeppelin ERC-20 patterns (7.1 Architecture). Code security is robust due to the use of audited, battle-tested libraries (7.2 Code Security). Access control is non-existent as the contract is permissionless (7.3 Access Control). External dependencies are limited to standard EIP interfaces (7.6 External).
There are no governance mechanisms or economic parameters defined within the contract (7.4 Economic, 7.5 Governance). The token supply is fixed upon deployment or managed via standard mint/burn logic. Operations are fully decentralized as there is no administrative control (7.8 Operations).
The contract is not upgradeable (7.7 Upgrades). It is a standard immutable deployment. No proxy patterns are utilized.
The contract is secure and follows industry best practices for standard tokens.
No further action is required for the current implementation. Ensure that any future integrations or extensions maintain the current permissionless nature of the contract to avoid introducing centralized points of failure.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Add your links and get it Verified
