SushiToken$SUSHI
Risk analysis for SushiToken (SUSHI) on Ethereum — contract 0x6b3595068778dd592e39a122f4f5a5cf09c90fe2. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Technical snapshot
Market structure, order flow and published on-chain evidence from one chain-specific snapshot.
Available depth relative to valuation
24h volume divided by liquidity
Transaction split unavailable
Across 1h, 6h and 24h returns
How to read these technicals
Turnover measures trading activity against available liquidity. High turnover can also mean volatility.
Momentum alignment compares overlapping return windows. It is context, not independent confirmation or a safety score.
Holder concentration uses the published report’s classified holder evidence when available.
Freshness is the age of Rug.Tools’ indexed market snapshot, separate from the report scan time.
Price chart
Live price chart for SUSHI is provided by DexScreener.
Market overview
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
0x87C7056BBE6084f03304196Be51c6B90B6d85Aa2The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is SushiToken?
SushiToken ($SUSHI) is a ERC-20 token on the Ethereum blockchain Its primary trading venue is sushiswap, with roughly $1.73M in live on-chain liquidity. It currently has 130,937 on-chain holders, and was first traded 3.5 years old. Rug.Tools' current assessment of SushiToken is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
SushiToken (SUSHI) is a Ethereum token analyzed by Rug.Tools. Current status: The token is actively trading, but one wallet holds 10.0% of supply, and the top 10 wallets control 37.2% of supply, and the creator has a concerning launch history, and new tokens can be minted.. Snapshot: ~$1,727,268 in on-chain liquidity, 130,937 holders, 1273 days old. This page auto-updates as new on-chain data is collected.
Rug.Tools signals
Key statistics
Rug.Tools analysis
The token is actively trading, but one wallet holds 10.0% of supply, and the top 10 wallets control 37.2% of supply, and the creator has a concerning launch history, and new tokens can be minted.
Verdict from canonical snapshot 2b59af35 · v3 · scanned 2026-09-30 21:46 UTC · page content updated 2026-09-30 21:46 UTC
Holder distribution
Creator profile
0xf942dba4159cb61f8ad88ca4a83f5204e8f4a6bdFull creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2023-04-06 04:53 UTCToken launchedFirst on-chain trading pair opened on sushiswap.
- 2026-09-30 21:46 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Compared using stored market cap, launch age and trading venue. Similarity is not a safety rating.
Finding comparable tokens…
Learn more
Frequently asked questions
What is SushiToken?⌄
SushiToken is a Ethereum token analyzed by Rug.Tools using public on-chain data — holders, liquidity, creator wallet activity and contract security signals. This page shows the latest cached analysis and refreshes automatically.
Is SushiToken safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but one wallet holds 10.0% of supply, and the top 10 wallets control 37.2% of supply, and the creator has a concerning launch history, and new tokens can be minted. No token can be guaranteed safe: verdicts summarize on-chain risk signals only and cannot detect off-chain intent. Always do your own research.
How many holders does SushiToken have?⌄
Rug.Tools currently sees 130,937 holders. The top individual wallet holds 10.02% of supply; the top 10 individual wallets together hold 37.20%.
Where is SushiToken traded?⌄
The primary trading venue detected on Ethereum is sushiswap. Use Rug.Tools Swap above to review a routed quote without leaving this report.
How often does this page update?⌄
This page renders from cached data in our database. It refreshes when a new scan runs — either on a scheduled background sync or when a user clicks Refresh above. Opening this page does not trigger a new scan.