
猫王
Risk analysis for 猫王 (猫王) on BNB Chain — contract 0x6181a161fa887b2f48cfcdb90be76b9adb9b7777. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-10-28 06:35 UTC
A Healthy rating could not be verified: critical contract-security fields are unknown; top-holder account identity is unverified; the underlying evidence is stale and has not been re-verified. This is not evidence the token is unsafe — the required checks did not resolve.
Reliability & unknowns
Low confidence describes evidence coverage, quality and freshness, not token safety. checks incomplete.
• Required verification checks are incomplete; category availability does not establish completed verification.
• The report evidence is stale or its observation time is invalid; confidence is limited.
• 0/7863 launch-wallet balances measured; 7863 remain unknown. Present group holdings are not fully measured.
• Contract Security: Required contract checks are incomplete; absence of critical flags is not established.
• Largest Holder Account: Largest sampled holder account holds 3.1%; independent control is unverified.
LP protection: check the full canonical report for independently verified lock, burn or withdrawal evidence. Indexed wiki flags alone do not prove protection.
Technical snapshot
Trading indicators and observed activity
Technical snapshot
Market data and stored security analysis are separate observations; check their timestamps before comparing numbers.
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
Price chart
Price chart
Load verified candle history to explore price and volume directly in this report.
Market overview
Market overview
Market data
Trading activity
Markets & liquidity pools
Markets & liquidity pools
Primary indexed pool
0xe1bbe7f41446d1B73c61AC5aBb7576A64B9e9110The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is 猫王?
What is 猫王?
猫王 ($猫王) is a BEP-20 token on the BNB Chain blockchain Its primary trading venue is pancakeswap, with roughly $283.96K in indexed market liquidity. Its displayed canonical holder snapshot reports 21,258 holder accounts, and was first traded 3 months old. Rug.Tools' stored assessment of 猫王, scanned 2026-10-28 06:35 UTC, is "Checks Incomplete". This verdict reflects the evidence available at the time, not current market conditions.
Rug.Tools signals
Rug.Tools signals
Key statistics
Key statistics
Launch activity
Native receipt, wallet and liquidity custody evidenceNative evidence explorer
Launch, wallet flows & liquidity custody
Inspect what was observed, which balances were measured, and what remains unverified. Timing and transfers alone do not establish common ownership or a sale.
Investigate creator trades & token transfers
Forensic intelligence / Activity
What did the developer actually do?
Separate current holdings, historical launch exposure, verified sales and token transfers. Follow the receipts before drawing conclusions.
- Creator holdings
- 0.00%
- Historical launch exposure
- 3.00%
Saved balance measurement; separate from sale history
Observed launch-group share of total token supply; not every graph node, developer sales or present insider ownership
Developer sales: Insufficient Evidence · Trading integrity: Not Scored. A creator holding 0% does not establish whether tokens were sold or transferred.
Launch evidence
60 stored cohort rows
Interval evidence only; full launch coverage is reported separately.
Receipt-level replay was not stored for this snapshot.
Current cohort balances
Unknown
0/7863 wallets measured · 7863 unknown
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x1ec3…f2b0 · 0.00% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xedc9…ef78
Launch timeline & receipt references
This older snapshot contains a recipient cohort, not the full receipt timeline. Counts and timing describe only the stored sample. Exact interval supply figures and transaction references remain unknown until a bounded native replay records them.
Pool-by-pool custody & protection
1.79% of token supply in custody · reported role / market
An infrastructure classification does not establish ownership or withdrawal protection for an individual liquidity position.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 40 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|---|---|---|
| 0xdfbc…5c42 | Unknown | #116,663,203 | Not stored |
| 0xcea2…3fb9 | Unknown | #116,663,389 | Not stored |
| 0x2842…2e98 | Unknown | #116,664,150 | Not stored |
| 0x63ce…4dc0 | Unknown | #116,666,983 | Not stored |
| 0x5a0a…807e | Unknown | #116,662,731 | Not stored |
| 0x1448…9db3 | Unknown | #116,665,513 | Not stored |
| 0x9745…ec57 | Unknown | #116,665,082 | Not stored |
| 0xe9ef…5c7f | Unknown | #116,662,485 | Not stored |
| 0x0c20…fd51 | Unknown | #116,662,619 | Not stored |
| 0xbc24…1b08 | Unknown | #116,662,455 | Not stored |
| 0xad6f…efcc | Unknown | #116,664,202 | Not stored |
| 0x8662…be5e | Unknown | #116,662,456 | Not stored |
| 0x67b5…cd13 | Unknown | #116,665,629 | Not stored |
| 0xb4af…9618 | Unknown | #116,664,653 | Not stored |
| 0xeeb6…9c7e | Unknown | #116,662,340 | Not stored |
| 0x9918…4d8f | Unknown | #116,662,200 | Not stored |
| 0x08e1…828a | Unknown | #116,662,200 | Not stored |
| 0x9df5…1875 | Unknown | #116,662,301 | Not stored |
| 0xcedf…5ae8 | Unknown | #116,662,324 | Not stored |
| 0xb5ed…97aa | Unknown | #116,662,259 | Not stored |
| 0x017c…7134 | Unknown | #116,664,135 | Not stored |
| 0x9cf1…c313 | Unknown | #116,662,231 | Not stored |
| 0x6e9c…17a9 | Unknown | #116,663,291 | Not stored |
| 0x2a9e…8294 | Unknown | #116,662,556 | Not stored |
| 0xf97f…1818 | Unknown | #116,666,223 | Not stored |
| 0x4cb0…594e | Unknown | #116,662,536 | Not stored |
| 0x3a29…a658 | Unknown | #116,662,304 | Not stored |
| 0xe467…1cd1 | Unknown | #116,662,548 | Not stored |
| 0xc83c…bbe0 | Unknown | #116,664,183 | Not stored |
| 0x999a…f1b6 | Unknown | #116,662,250 | Not stored |
| 0x3637…7ff7 | Unknown | #116,667,132 | Not stored |
| 0x3c85…cb60 | Unknown | #116,662,509 | Not stored |
| 0xea4c…3321 | Unknown | #116,662,281 | Not stored |
| 0xa23c…577e | Unknown | #116,662,217 | Not stored |
| 0x08af…aa8b | Unknown | #116,662,217 | Not stored |
| 0xb833…a15a | Unknown | #116,662,217 | Not stored |
| 0xcce2…c175 | Unknown | #116,662,326 | Not stored |
| 0xab56…2725 | Unknown | #116,663,175 | Not stored |
| 0xbf73…056b | Unknown | #116,662,329 | Not stored |
| 0x8d28…ce79 | Unknown | #116,662,866 | Not stored |
Source snapshot: . This evidence explorer does not independently change the Rug.Tools verdict. Existing risk findings, verification gates and source timestamps remain authoritative.
RugGraph / Wallet intelligenceLinked-wallet graph25 wallets · 1 transaction references. Follow the receipts from saved launch evidence.Open wallet graph ↓
01 / Launch activity
Select a wallet to see its activity near token launch. Early receipt of tokens alone does not prove a sniper purchase.
Cyan: tokens received · Amber: tokens moved out · Dashed: deployment. Lines connect wallets to the launch sample; they do not identify who sent the tokens. The first 12 wallets are plotted; every listed wallet can be inspected below.
0x1ec30ff00d3671f40375782af24350562740f2b0
Creator attribution
Balance at last observation
Unknown
Time unavailable · observation, not a live balance
02 / Funding connections
Where did the funding come from?
Follow verified transfers back up to three wallets. Select any connected wallet to explore its evidence.
Enhanced funding history is unavailable on this chain or snapshot. The saved report remains available above.
Evidence first. Ownership stays unproven.
A transfer proves funds moved between addresses. It does not prove they belong to the same person. Known exchange, bridge and pool accounts are marked as infrastructure.
How to read this evidence
Arrows show receipt references associated with the launch sample. They do not identify transfer counterparties or establish common ownership.
An early recipient is not necessarily a buyer or sniper. Outflows may be transfers; these summaries do not establish realized sales.
Balance measurements retain their original timestamps. Historical launch exposure is separate from present holdings.
Funding paths, verified swap activity and volume manipulation require additional transaction evidence. Missing history is unknown.
Source snapshot: 2026-10-28 06:35:26 UTC · Funding research runs only when requested.
Rug.Tools analysis
Rug.Tools analysis

A Healthy rating could not be verified: critical contract-security fields are unknown; top-holder account identity is unverified; the underlying evidence is stale and has not been re-verified. This is not evidence the token is unsafe — the required checks did not resolve.
- Contract Security: Required contract checks are incomplete; absence of critical flags is not established.
- Project Lifecycle: Project is actively trading on-chain.
- Largest Holder Account: Largest sampled holder account holds 3.1%; independent control is unverified.
- Sampled Holder Accounts: sampled holder accounts hold 9.6% — low concentration.
- Liquidity: Liquidity depth looks reasonable ($283,962).
Verdict from canonical snapshot 5d05b2b2 · v3 · scanned 2026-10-28 06:35 UTC · page content updated 2026-10-28 06:35 UTC
Holder distribution
Holder distribution
Holder figures from the canonical report; observed 2026-10-28 06:35 UTC. They may be older than the market snapshot.
Only recorded top-ten shares are shown; remaining supply, infrastructure custody, and control are not inferred.
Creator profile
Creator profile
0x1ec30ff00d3671f40375782af24350562740f2b0Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2026-08-18 13:12 UTCToken launchedFirst on-chain trading pair opened on pancakeswap.
- 2026-10-28 06:35 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
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
Frequently asked questions
What is 猫王?⌄
猫王 is a BNB Chain token analyzed by Rug.Tools using available public on-chain data. Holder observations, indexed market data, and the stored risk verdict may have different observation times.
Is 猫王 safe?⌄
Stored Rug.Tools verdict: Checks Incomplete (scanned 2026-10-28 06:35 UTC). A Healthy rating could not be verified: critical contract-security fields are unknown; top-holder account identity is unverified; the underlying evidence is stale and has not been re-verified. This is not evidence the token is unsafe — the required checks did not resolve. A stored verdict does not prove current safety or future intent. Always do your own research.
How many holders does 猫王 have?⌄
The displayed canonical report holder data reports 21,258 holders, largest measured holder 3.08% and top ten 9.57%. Holder observation: 2026-10-28 06:35 UTC. These figures are historical measurements, not proof of independent control.
Where is 猫王 traded?⌄
The primary trading venue detected on BNB Chain is pancakeswap. Review the market and liquidity evidence below; trading venue availability does not establish token safety.
How often does this page update?⌄
This page shows cached reports and indexed market observations. Values change when new evidence is recorded or published; opening the page does not trigger a scan.