Trade with care. Read the warnings first.
A test sale worked on the pools we tested, but that does not show whether the pool's hook can stop a sale.
Scanned 2d ago. Scan again before you trade.
- WARNHoneypot
- WARNChecks with missing data
DexProof recorded MARIAN as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1358 published 28 Oct 2026 (UTC). Of 28 checks, 22 passed, 2 warned and 4 could not be run.
Trade with care. Read the warnings first.
A test sale worked on the pools we tested, but that does not show whether the pool's hook can stop a sale.
Scanned 2d ago. Scan again before you trade.
Price
$0.0002
Liquidity
$73,188
Volume 24h
$1,548
FDV
$231,968
Buys 24h
15
10 sells
Age
137d 7h
A test sale worked on the pools we tested, but that does not show whether the pool's hook can stop a sale.
Sells on this pool go through a swap hook we could not verify. Our code check found no owner-set sell controls, but that does not show what the hook does to a sale.
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.
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 didn't check 54 transactions by the creator that could remove liquidity.
The creator's wallet was funded by , a shared source that has sent starting funds to 22 different wallets.
A shared source such as an exchange funds many unrelated people, so its record does not name any one of them.
We couldn't read this pool's liquidity history, so we couldn't check who holds its liquidity.
This pool is on Uniswap V3 and holds 99.1% of the liquidity we could read. 4 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
This deployer was funded by , a wallet that has sent starting funds to 22 different wallets.
That is a shared source such as an exchange, so its history says nothing about this deployer.
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.
This deployer has no earlier launches on record.
Top 10 holders hold 25% of the tokens in circulation.
Against total supply, the top 10 hold 20.2%. Liquidity pools hold 20.1% 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. 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.
Ownership was renounced.
The owner is the zero or dead address.
The deepest pool holds $73,188.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is verified on the explorer, but it was matched from another address with identical bytecode, not proven against this one.
This token's value at full supply is 3× its pool liquidity, a proportionate ratio.
We found no privileged powers in the token contract's code.
We looked at its audited source and compiled code.
Trading volume over 24 hours is 0.0× the pool's liquidity, below our warning level.
Volume is 0.0× the pool's liquidity, below our warning level.
Our market data had no trader counts, so we could not check for wallets trading back and forth.
We saw no fee or limit changes by the deployer in the transactions we searched.
We only looked at the deployer's recent history, so changes by a separate fee owner would not show.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This token's code doesn't match any code template we know of.
This token's pool was 135 days old at this scan.
This contract was 135 days old at this scan.
No launchpad deployed this token.
It was deployed directly, which counts neither for nor against it. The on-chain checks decide this one.
The source is verified, so anyone can read the code.
We could not match it to a known template.