DeepGyre/Scanner/CAPE on Solana

Capecoin (CAPE)

SolanaGMDaSAbntf9ZTGvnAj53Vn3pSRVo6oe6NaiKLYy9pump
60/100
risk score — MEDIUM
0.0% / 0.0%
buy / sell tax
$4K
DEX liquidity
3
times scanned on DeepGyre

Checks

Honeypot (cannot sell)no
Cannot sell allnot measured
Owner can mintnot measured
Hidden ownernot measured
Owner can change balancesnot measured
Blacklist functionnot measured
Transfers can be pausednot measured
Ownership renouncednot measured
Upgradeable proxyno
Source code verifiedno
Holders—
24h volume$439K

What this scan covers

The scanner reads the token's contract on Solana and runs the checks you see above: can a holder actually sell (the honeypot simulation trades against the same pool a buyer would, without signing anything), what the buy and sell taxes really are when a transfer executes, whether the owner can mint, pause, blacklist or rewrite balances, whether ownership is renounced or behind a proxy, and how deep the liquidity is against how concentrated the largest holders are.

Every check has three possible answers — yes, no, and not measured. A check the contract shape does not allow, or a value the chain did not answer at scan time, prints "not measured" rather than a misleading no. The risk score is a weighted read of these factors, shown with the factors and their impact so the number can be argued with instead of trusted.

Frequently asked

A check says "not measured" — is that bad?

Neither good nor bad: the scan could not read it, so it refuses to guess. Re-scan the token live to try again against the current block.

Does a good score mean the token is safe?

No. It means none of the measured red flags fired. A contract can still be renounced today and its liquidity pulled tomorrow — scores age, checks do not predict.

Why does the page show a stored scan instead of a fresh one?

So opening the page is free of side effects: the scanner's upstream budget is spent when you ask for a live scan, not when someone reads this one.

This is the most recent stored scan, taken 2026-10-22 17:03 UTC (first scanned 2026-10-22 10:59 UTC). A token can change after a scan — re-scan it before acting.

Re-scan CAPE live →
Descriptive, not advice. Every score is an automated heuristic over public data and can be wrong in both directions. Methodology · Dashboard