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 | 13 Nov 2026 |
| Buy tax | 0% | Contract | 13 Nov 2026 |
| Sell tax | 0% | Contract | 13 Nov 2026 |
| Admin mint | Not present | Contract | 13 Nov 2026 |
| Transfers pausable | Not present | Contract | 13 Nov 2026 |
| Address blacklist | Not present | Contract | 13 Nov 2026 |
| Upgradeable proxy | No | Contract | 13 Nov 2026 |
| Source verified | Yes | Block explorer | 13 Nov 2026 |
| Top-10 holders | 50% | Holder distribution | 13 Nov 2026 |
| Liquidity locked | No | LP holders | 13 Nov 2026 |
| Holders | 8829 | Token contract | 13 Nov 2026 |
| Deployed by | 0x4f9d4b…ffcb8d |
| Holders | 8,829 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x73d8bd…4946db | 28.56% |
| #2 · contract | 0x60c68b…d00384 | 8.28% |
| #3 · PancakeV3 · contract | 0x7a907a…fb7eed | 3.16% |
| #4 · contract | 0x238a35…d5e6c4 | 2.53% |
| #5 · contract | 0x1fce5a…17cd7e | 1.58% |
This automated check scanned the GSTOCK contract on BSC and found a score of 14 out of 18. In practical terms, a transfer simulation showed the token could be sold at the time of testing, with no buy or sell tax detected. The contract does not contain a mint function, so the owner cannot currently create new tokens out of thin air and dilute holders. No pause function was detected, meaning transfers cannot be frozen by the contract owner, and no blacklist function was found, so addresses cannot be selectively blocked from trading. The contract is also not an upgradeable proxy, which means its logic cannot be swapped out for different code after the fact. Two points stand out as risk indicators: the top 10 wallets hold 50% of total supply, which is a high concentration — if any of those wallets sell in size, it could move the price sharply — and the liquidity backing the token is not locked, meaning whoever controls that liquidity pool could withdraw it, which would make the token difficult or impossible to sell at a fair price.
It's worth being clear about what this check does not cover. This is a purely mechanical read of the contract's code and on-chain data as they existed on the date of the check. It says nothing about who is behind the project, whether the team has a history of delivering on claims, how the token's supply is actually structured or vested, whether any legal or regulatory wrapper exists, or what the team's intentions are. A contract can look technically clean by every measure above and still be part of a project with poor fundamentals or bad-faith actors behind it. Conversely, a flagged item doesn't automatically mean harm is intended — it means the capability exists and hasn't been ruled out.
Given these findings, a reasonable next step would be to look at who holds that top 50% of supply and whether those wallets are tagged as team, exchange, or treasury addresses — the block explorer's holder list is a good starting point. It's also worth checking whether the liquidity pool tokens are held in a known wallet versus a locking contract, since unlocked liquidity sitting with a single address is a materially different situation to liquidity held by a reputable third-party locker. Beyond the contract itself, reviewing the project's public communications, any audit reports from named firms, and the team's identity and track record would sit outside the scope of this check but are relevant to forming a fuller picture.
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 18 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.