Trade with care. Read the warnings first.
Top 10 holders hold 100% of the tokens in circulation.
- FAILHolder concentration
- WARNHoneypot
- WARNChecks with missing data
DexProof recorded RMT as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1687 published 31 Oct 2026 (UTC). Of 28 checks, 13 passed, 2 warned, 1 failed and 12 could not be run.
Trade with care. Read the warnings first.
Top 10 holders hold 100% of the tokens in circulation.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Top 10 holders hold 100% of the tokens in circulation.
The largest holder is , a contract, holding 83.8% of the tokens in circulation for other holders we could not list. That share is not proven to be under one key. Some of these tokens sit inside a staking or escrow contract, and we could only partly tell who deposited them. We report the highest share the evidence supports.
We found no Uniswap V3 pool paired with ETH, so we couldn't run a sell test there.
We couldn't read some checks on this scan, so the verdict is limited.
A failed read is not a clean result. This describes what we could see, not the token.
These are gaps in what we could see, not problems found in this token.
We found no pool for this token on V2, V3 or V4, so there were no liquidity removals to read.
The LP custody check could not read this token's pools either, so we don't know who can pull its liquidity.
Applies to: Funder rug history, Deployer launch history, Funding lineage, Tax manipulation
So we can't check for past rugs, because many people launch through it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check its past launches. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't trace who funded it. The transaction that created it was sent by , but a transaction sender can be the pad's own relayer rather than the launcher, so we don't attribute any history to that address.
So we can't check whether it changed fees or limits.
A contract deployed this token, but that contract is not in the launchpad registry.
So we can't tell where it launched.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
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.
The contract has no owner function, so it has no single owner wallet.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is verified on the explorer.
This is about its implementation at .
We found no privileged powers in the token contract's code.
We looked at its audited source and compiled code.
No paid promotion found on DexScreener.
This token's code doesn't match any code template we know of.
This contract was 108 days old at this scan.
The source is verified, so anyone can read the code.
We could not match it to a known template.
This token has never traded, so there is no pool liquidity for us to check.
Applies to: Liquidity depth, FDV vs liquidity ratio, Volume turnover, Wash trading, Pool age
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.
We found no pool for it on any exchange we cover.