Scanner / Robinhood Chain / 0xdb90…da7b
MUSEPADMusepad
Scanned Thu, 17 Sep 2026 09:12:08 GMT. This page re-runs the scan when it is opened, so the verdict reflects the chain as it is now, not when the link was shared.
Liquidity is not locked
6 risk signals found, 3 checks passed. Scored 38/100.
What Nebula could not verify
- GeckoTerminal rate-limited this request, so holder distribution and deployer stake were not checked on this run. Reload in a minute for the full picture.
- No sell simulation is available on this chain — nobody has proven the token can actually be sold.
Contract analysis
read directly from the chainNo privileged functions matched in the deployed bytecode. Absence is not proof — unusual dispatch or hand-written assembly can hide one — but nothing in the standard set is present.
Risk signals
worst firstOnly 0.0% of LP tokens are locked or burned. The rest can be pulled from the pool at any moment.
Most rugs happen inside the first day. History is too short to mean much.
24h volume is 21.6x pool liquidity. Some of this is likely inorganic.
$92.1K of depth across 16 pools — modest, so size accordingly.
Up 951% in 24h. Late entries carry the risk.
Nothing published on the pair. No team, no roadmap, nobody accountable.
Checks passed
Liquidity is 17.7% of market cap across 16 pools — deep enough to absorb normal selling.
The contract exposes no owner() or getOwner(), so there is no admin role to abuse.
Direct analysis of 3,248 bytes of deployed code found no ownership function, no upgrade proxy, and no mint, pause or blacklist capability. This is what a fixed-supply token with nothing hidden behind it looks like.
All liquidity pairs
split liquidity is easy to misread as depthCheck another token
Paste any address on Robinhood Chain, Ethereum, Base, BNB Chain, Arbitrum or Solana.