Free above: contract permissions, sell test and tax when data is available.
Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.
| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | ChainSift simulation | 15 Nov 2026 |
| Buy tax | 0% | ChainSift simulation | 15 Nov 2026 |
| Sell tax | 0% | ChainSift simulation | 15 Nov 2026 |
| Admin mint | No data | Contract | 15 Nov 2026 |
| Transfers pausable | No data | Contract | 15 Nov 2026 |
| Address blacklist | No data | Contract | 15 Nov 2026 |
| Upgradeable proxy | No data | Contract | 15 Nov 2026 |
| Source verified | No | Block explorer | 15 Nov 2026 |
| Top-10 holders | 76.2% | Holder distribution | 15 Nov 2026 |
| Liquidity locked | No | LP holders | 15 Nov 2026 |
| Holders | 181 | Token contract | 15 Nov 2026 |
| Deployed by | 0x65ea4a…fbb1bf |
| Holders | 181 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x639fa2…e18bc1 | 60.17% |
| #2 | 0xa396d9…7ffba4 | 2.40% |
| #3 | 0xfe65f0…005c51 | 2.32% |
| #4 | 0xb1b673…00179a | 2.14% |
| #5 | 0x5bbdab…6302f6 | 1.95% |
This automated check scored GTA6 1 out of 10 on the date it was run, and it's worth understanding exactly what that low score is and isn't telling you. The simulation found that selling was possible, with no buy or sell tax detected — meaning the test transaction wasn't blocked and no hidden fee was charged at the time of the check. However, because the contract's source code is not verified, ChainSift could not read the actual logic behind functions like minting, pausing transfers, blacklisting addresses, or upgrading the contract itself — these all show as "no data" because the bytecode alone doesn't reveal them. In practice, this means there could be hidden functions that let whoever controls the contract mint new tokens and dilute holders, freeze transfers, block specific wallets from selling, or swap in entirely new contract logic after the fact — none of this can be ruled in or out from bytecode alone. Add to that the fact that liquidity is not locked, which means whoever holds the liquidity pool tokens could remove that liquidity at any time, and that the top 10 holders control 76.2% of supply, giving a small number of wallets the ability to move the market significantly if they sell. With only 181 holders recorded, this is a thinly distributed token.
What this check does not tell you is just as important. It only reads contract mechanics and on-chain data as they existed at the time of the scan — it says nothing about who is behind the project, what their intentions are, whether marketing claims match reality, or whether any legal or business structure exists around the token. No human has reviewed this contract or the team behind it; this is purely an automated read of code and holder data. A token can show no honeypot behaviour and still carry substantial risk from unverified code, concentrated holdings, or unlocked liquidity.
Before considering any transaction, you may want to look at whether the contract has been verified on the relevant block explorer since this check was run, look up the liquidity pool directly to see who holds the LP tokens and whether a lock exists with a visible unlock date, and research the top holder wallets to see if they are known exchange or team addresses versus unrelated individual wallets. You could also look for any independent audit of the actual source code, since bytecode-only analysis has firm limits. None of this removes the uncertainty created by unverified source code and unlocked liquidity, but it may help you understand the shape of the risk before making any decision.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 10 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.