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 | Transfer simulation | 14 Nov 2026 |
| Buy tax | 0% | Contract | 14 Nov 2026 |
| Sell tax | 0% | Contract | 14 Nov 2026 |
| Admin mint | Not present | Contract | 14 Nov 2026 |
| Transfers pausable | Not present | Contract | 14 Nov 2026 |
| Address blacklist | Not present | Contract | 14 Nov 2026 |
| Upgradeable proxy | No | Contract | 14 Nov 2026 |
| Source verified | Yes | Block explorer | 14 Nov 2026 |
| Liquidity locked | 100% burned | LP holders | 14 Nov 2026 |
| Holders | 201 | Token contract | 14 Nov 2026 |
| Deployed by | 0xbe7960…409dc4 |
| Holders | 201 |
| Rank | Address | Share |
|---|---|---|
| #1 · Uniswap v4 pool · contract | 0x000000…e08a90 | 80.73% |
| #2 · contract | 0x000000…707555 | 18.97% |
| #3 | 0x686310…19bc30 | 11.01% |
| #4 · contract | 0x410144…0ea4a3 | 4.98% |
| #5 | 0xea044f…35b64a | 4.27% |
This automated check scanned the GTA6 (GTA VI) contract on Ethereum and did not detect several mechanisms that are commonly used to restrict or disadvantage holders. A transfer simulation indicated the token was sellable at the time of the check, and buy and sell tax were both read as 0% directly from the contract. No admin mint function was found, meaning no mechanism was detected that would let the contract owner create new tokens and increase supply at will. No pause function was detected, so no mechanism was found that would let transfers be switched off. No blacklist function was detected, which would otherwise allow specific wallet addresses to be blocked from trading. The contract is not an upgradeable proxy, meaning its logic cannot be swapped out for different code after the fact without deploying an entirely new contract. The source code is verified on the block explorer, so the logic described above is publicly readable rather than hidden behind unverified bytecode. Liquidity is reported as 100% burned, meaning the LP tokens representing claim on the trading pool were sent to an address with no known private key, which is read here as reducing the likelihood of that specific pool being pulled by whoever created it.
It's worth being clear about what this does not cover. This check reads contract mechanics only — the code's permissions and behaviour at the time of the scan. It says nothing about who is behind the project, whether the team has a history in other tokens, how the token's supply is distributed or scheduled to unlock, whether there are off-chain promises or agreements, or whether the stated intent of the project matches what eventually happens. A clean mechanical read is not an assessment of the people running it or the economic design of the token, and findings reflect conditions on the date of the check only; contract-level permissions and liquidity status can both change later through actions outside this scan's visibility.
Before deciding anything, it's worth looking at how the 112 holders are distributed — a small number of wallets holding a large share of supply is a separate risk from anything the contract code shows. It's also worth checking whether the liquidity pool itself is deep enough that a sale of meaningful size wouldn't move the price sharply, looking into who the team is and whether they're identifiable, searching for independent discussion of the project outside its own channels, and checking whether the burn address and lock details can be independently verified on the block explorer rather than taken on trust from a single source.
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 12 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.