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 | 20 Nov 2026 |
| Buy tax | 0% | Contract | 20 Nov 2026 |
| Sell tax | 0% | Contract | 20 Nov 2026 |
| Admin mint | Not present | Contract | 20 Nov 2026 |
| Transfers pausable | Not present | Contract | 20 Nov 2026 |
| Address blacklist | Not present | Contract | 20 Nov 2026 |
| Upgradeable proxy | No | Contract | 20 Nov 2026 |
| Source verified | Yes | Block explorer | 20 Nov 2026 |
| Top-10 holders | 94.3% | Holder distribution | 20 Nov 2026 |
| Liquidity locked | No | LP holders | 20 Nov 2026 |
| Holders | 55584 | Token contract | 20 Nov 2026 |
| Deployed by | 0xd23b7d…eec3ef |
| Current owner | None — ownership renounced |
| Holders | 55,584 |
| Rank | Address | Share |
|---|---|---|
| #1 · PancakeV3 · contract | 0x9485ff…7075a2 | 49.29% |
| #2 · burned | 0x000000…00dead | 20.77% |
| #3 | 0x16f17e…3bcc6d | 11.27% |
| #4 · contract | 0x73d8bd…4946db | 6.32% |
| #5 · PancakeV3 · contract | 0xd28c09…caa8c1 | 3.86% |
This automated check looked at quq's contract code and current on-chain data, and scored it 12 out of 18. In practical terms, a few things were tested directly: a simulated transfer showed the token can currently be sold, and both the buy and sell tax are set to 0%, so no hidden fee was detected that would quietly eat into trades. The contract does not appear to give the owner the ability to mint new tokens, pause transfers, or blacklist specific addresses — meaning, as of this check, none of those controls were found in the code that would let whoever deploys or controls the contract freeze a holder's tokens, stop trading, or dilute supply at will. The contract is also not upgradeable, so its current rules can't later be swapped for different ones through a proxy mechanism. The source code is verified on the block explorer, which means the code humans can read matches what's actually running on-chain, though this check did not involve a person reviewing that code for subtler issues.
Two points stand out as worth attention rather than reassurance. Liquidity in the main pool is not locked, and while the check notes this is common for large tokens with many liquidity providers (30 in this case), it still means there's no contractual guarantee preventing a provider from withdrawing liquidity. Separately, the top 10 holders control 94.3% of supply — a concentration level that means a small number of wallets could move a large share of tokens, which can affect price and liquidity regardless of what the contract code allows or restricts.
It's worth being clear about what this check does not cover. It reads contract mechanics and on-chain data only — it says nothing about who the team behind quq is, whether they have a track record, how tokens were allocated or vested, what the project claims to do, or whether any of it is legally structured or compliant where you live. None of that intent or context is assessed here, and no human has reviewed this token beyond what the automated scan produced.
Before putting any money in, it would be sensible to look into who holds those top 10 wallets and whether any are known exchange or team addresses, to search for independent discussion of the project outside its own channels, to check whether liquidity providers have any history of withdrawing early from similar pools, and to review any available audit, whitepaper, or team disclosure separately from this contract-level check.
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.