DeepGyre/Scanner/LATI on BNB Chain

Latitude (LATI)

BNB Chain0xC5f56b20829B43Eb3Afb2a6D49f3508f88C08dCE
25/100
risk score — LOW RISK
0.0% / 0.0%
buy / sell tax
—
DEX liquidity
4
times scanned on DeepGyre

Checks

Honeypot (cannot sell)no
Cannot sell allno
Owner can mintno
Hidden ownerno
Owner can change balancesno
Blacklist functionno
Transfers can be pausedno
Ownership renouncedyes
Upgradeable proxyno
Source code verifiedyes
Holders220
24h volume—

What moved the score

FactorImpact
No Liquidity
No DEX liquidity found
+80
Ownership Renounced
No central control point
-20
Moderate Concentration (66% top-10)
Top 10 hold >60%
+15
No Age Data
Cannot verify contract history
+15
Counterfeit: mint without supply update
Mint/balance-increase path does not update totalSupply — created coins never appear in the declared supply (shadow inflation).
+12
Source Verified
Code is publicly auditable
-10
Listed on DEX
Active DEX presence
-5

What this scan covers

The scanner reads the token's contract on BNB Chain 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 16:05 UTC (first scanned 2026-10-22 16:00 UTC). A token can change after a scan — re-scan it before acting.

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