Chiiba-kun$チーバくん
Risk analysis for Chiiba-kun (チーバくん) on BNB Chain — contract 0x1067d3a9153559f4ab16840ba2c317c29a7b7777. 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 チーバくん is provided by DexScreener.
Market overview
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
0x8942228C18a59c6879181ac8fe8ACe01e191507DThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Chiiba-kun?
Chiiba-kun ($チーバくん) is a BEP-20 token on the BNB Chain blockchain Its primary trading venue is pancakeswap, with roughly $10.69K in live on-chain liquidity. It currently has 326 on-chain holders, and was first traded 12 days old. Rug.Tools' current assessment of Chiiba-kun is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
Chiiba-kun (チーバくん) is a BNB Chain token analyzed by Rug.Tools. Current status: Multiple health signals are weakening, and the top 10 wallets hold 18.1% of supply, and liquidity is relatively low, so expect slippage when trading.. Snapshot: ~$10,691 in on-chain liquidity, 326 holders, 4 days old. This page auto-updates as new on-chain data is collected.
Rug.Tools signals
Key statistics
Rug.Tools analysis
Multiple health signals are weakening, and the top 10 wallets hold 15.8% of supply, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 13.7% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot edd7ac90 · v3 · scanned 2026-09-23 20:03 UTC · page content updated 2026-09-26 13:05 UTC
Holder distribution
Creator profile
0x883fb80269c30d3496b23b8751e846c34222ac33Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2026-09-21 15:26 UTCToken launchedFirst on-chain trading pair opened on pancakeswap.
- 2026-09-26 13:05 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Loading similar BNB Chain tokens…
Learn more
Frequently asked questions
What is Chiiba-kun?⌄
Chiiba-kun is a BNB Chain 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 Chiiba-kun safe?⌄
Current Rug.Tools verdict: Elevated Risk. Multiple health signals are weakening, and the top 10 wallets hold 15.8% of supply, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 13.7% of supply, but independent wallet linkage is not fully corroborated. 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 Chiiba-kun have?⌄
Rug.Tools currently sees 326 holders. The top individual wallet holds 3.18% of supply; the top 10 individual wallets together hold 18.10%.
Where is Chiiba-kun traded?⌄
The primary trading venue detected on BNB Chain is pancakeswap. 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.