Trade with care. Read the warnings first.
Top 10 holders hold 100% of the tokens in circulation.
Scanned 2d ago. Scan again before you trade.
- FAILHolder concentration
- WARNHoneypot
- WARNChecks with missing data
DexProof recorded DIME as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1384 published 28 Oct 2026 (UTC). Of 28 checks, 13 passed, 5 warned, 1 failed and 9 could not be run.
Trade with care. Read the warnings first.
Top 10 holders hold 100% of the tokens in circulation.
Scanned 2d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Top 10 holders hold 100% of the tokens in circulation.
The largest holder is , a plain wallet, holding 72.9% of the tokens in circulation on its own. Against total supply, the top 10 hold 0.3%. Liquidity pools hold 99.7% of total supply, and we leave them out of the tokens in circulation. The top 10 share also moves when pool liquidity moves, even if no holder trades.
We couldn't finish the sell test on the other exchanges we checked.
The token's main pool did not pass a sell test, so smaller pools that did pass can't show the token can be sold.
We couldn't work out who controls this token's liquidity on this scan.
Missing data limits the verdict. A pool we couldn't read is not a pool we cleared. This describes what we could see, not the token.
This contract still has an active owner: .
The token contract has privileged powers (limit change, a switch that can block transfers or selling, privileged low-level code we couldn't read), but whoever controlled them gave up control or can no longer use them.
The code still contains these, but they can no longer be used: supply mint (initialize can only run once and already has), amm route change (initialize can only run once and already has), initialization (initialize can only run once and already has).
The same code has been deployed 15 times, which looks like a copycat pattern.
These are gaps in what we could see, not problems found in this token.
We can't rule out that the creator pulled liquidity from this token's pool.
We only read the creator's most recent transactions. We didn't check 615 transactions by the creator that could remove liquidity.
100.0% of the liquidity we could read is in a Uniswap V4 pool where its liquidity is locked, but a smaller pool has a problem.
We skipped this pool: it is one of 9 V4 pools for this token, outside the 6 with the most liquidity. We checked the pools that back the price instead. One other pool charges a fee too large to trade through, so nothing a holder owns is at risk there.
We found no active rug markers in the funding records we checked, but we couldn't trace every wallet linked to this deployer.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
A contract created this token, so we can't see the person behind it.
So we can't check whether it changed fees or limits.
We could not find when this token's pool was created.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
Nothing on record ties , the wallet that funded the creator, to a past rug on Robinhood Chain.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This token has no pump-and-dump mark in our records.
This deployer has no earlier launches on record.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is partially verified on the explorer.
The code matches, but the compiler metadata does not. This is about its implementation at .
No paid promotion found on DexScreener.
This contract was 61 days old at this scan.
Launched on Doppler.
Our launchpad records don't show it graduating, but it has a DEX pool. The raise on record is too old to compare against, so how much of it the creator bought is unknown.
The source is partially verified through a bytecode match, so the code can be read.
We could not match it to a known template.