RUG.TOOLS
哈基米
Risk analysis for 哈基米 (哈基米) on BNB Chain — contract 0x82ec31d69b3c289e541b50e30681fd1acad24444. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-10-18 19:45 UTC
- 1.Holder concentration
The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable.
Why it matters: This is a recorded report observation, not a prediction of future trading or intent.
- 2.Historical launch exposure
A sampled launch-window group of 310 tracked wallets reached up to 8.41% of supply.
Why it matters: Historical exposure does not prove common wallet control, and it cannot be added to current holdings.
- 3.Reported liquidity depth
$1,802,774.14 in tracked liquidity in the recorded market snapshot.
Why it matters: Trading depth affects slippage and exit difficulty. Market-reported liquidity does not establish a verified LP lock or current executable quote.
See 2 additional recorded findings
- 4. Top 10 individual wallet concentration
The reported top 10 individual wallets hold 71.49% of supply, using the report's holder classification and coverage.
Why it matters: Concentration can increase potential sell pressure. Wallet addresses do not establish distinct beneficial owners or independent control.
- 5. Creator wallet holdings
The identified creator wallet has 0.00% of supply in the recorded balance observation.
Why it matters: This measures the identified wallet only; it does not prove related-wallet holdings, creator intent, or future sales.
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/310 launch-wallet balances measured; 310 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 55.63%; 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
0xc33bACFf9141Da689875e6381c1932348aB4c5CBThe 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 $1.80M in indexed market liquidity. Its displayed canonical holder snapshot reports 67,715 holder accounts, and was first traded 1.1 years old. Rug.Tools' stored assessment of 哈基米, scanned 2026-10-18 19:45 UTC, is "High Risk". 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
- 8.41%
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/310 wallets measured · 310 unknown
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x05f0…848c · 0.00% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xa5ae…ed00
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
Pool allocation not established · reported role / market
Market selection alone does not verify LP ownership, locks or the controller of this pool.
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 |
|---|---|---|---|
| 0xedcf…ad6b | Unknown | #63,837,380 | Not stored |
| 0x1d75…dbe3 | Unknown | #63,837,851 | Not stored |
| 0xbeb7…2a96 | Unknown | #63,838,521 | Not stored |
| 0xc4cc…2fdd | Unknown | #63,839,661 | Not stored |
| 0x4f64…3db5 | Unknown | #63,838,476 | Not stored |
| 0xe885…6bbd | Unknown | #63,837,666 | Not stored |
| 0x381a…8168 | Unknown | #63,839,502 | Not stored |
| 0x9401…68da | Unknown | #63,838,322 | Not stored |
| 0xaeca…ddc9 | Unknown | #63,836,088 | Not stored |
| 0xe8ba…bcda | Unknown | #63,838,815 | Not stored |
| 0xa2d5…105d | Unknown | #63,840,977 | Not stored |
| 0x9a15…747f | Unknown | #63,838,551 | Not stored |
| 0xd2c1…8760 | Unknown | #63,839,164 | Not stored |
| 0x2c65…db78 | Unknown | #63,838,232 | Not stored |
| 0xbc7a…a303 | Unknown | #63,836,261 | Not stored |
| 0x6043…9b52 | Unknown | #63,839,186 | Not stored |
| 0x472d…4c06 | Unknown | #63,837,389 | Not stored |
| 0x8798…8db1 | Unknown | #63,836,985 | Not stored |
| 0x628d…c5c7 | Unknown | #63,838,829 | Not stored |
| 0x4228…be36 | Unknown | #63,836,111 | Not stored |
| 0xd122…7f37 | Unknown | #63,836,284 | Not stored |
| 0xd6c8…474c | Unknown | #63,836,612 | Not stored |
| 0x8da5…bb76 | Unknown | #63,836,410 | Not stored |
| 0xeb02…972e | Unknown | #63,836,639 | Not stored |
| 0xf71d…e773 | Unknown | #63,836,130 | Not stored |
| 0xe604…6eb8 | Unknown | #63,838,480 | Not stored |
| 0xcaed…9766 | Unknown | #63,838,954 | Not stored |
| 0x8320…2dd6 | Unknown | #63,837,181 | Not stored |
| 0x5a36…4257 | Unknown | #63,837,923 | Not stored |
| 0x2e07…3ee8 | Unknown | #63,840,346 | Not stored |
| 0x028c…376a | Unknown | #63,836,238 | Not stored |
| 0x0edb…7a04 | Unknown | #63,839,295 | Not stored |
| 0xa8e6…f033 | Unknown | #63,839,752 | Not stored |
| 0xb9e8…53ad | Unknown | #63,839,009 | Not stored |
| 0xe8e3…a9ea | Unknown | #63,840,997 | Not stored |
| 0x207b…a6fd | Unknown | #63,839,006 | Not stored |
| 0x1cc4…59dc | Unknown | #63,839,118 | Not stored |
| 0x4513…d3f0 | Unknown | #63,836,672 | Not stored |
| 0x218e…f92b | Unknown | #63,840,025 | Not stored |
| 0xe131…61c1 | Unknown | #63,837,103 | 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.
0x05f04a08df246ce66d04b718c343f7190fe0848c
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-18 19:45:26 UTC · Funding research runs only when requested.
Rug.Tools analysis
Rug.Tools analysis
The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable.
- Liquidity: Liquidity depth looks reasonable ($1,802,774).
- Project Lifecycle: Project is actively trading on-chain.
- Contract Security: Required contract checks are incomplete; absence of critical flags is not established.
- Largest Holder Account: Largest sampled holder account holds 55.63%; independent control is unverified.
- Sampled Holder Accounts: 10 sampled accounts hold 71.49% in total; this is a lower bound when the filtered sample has fewer than ten accounts.
Verdict from canonical snapshot 1e7e91ab · v3 · scanned 2026-10-18 19:45 UTC · page content updated 2026-10-18 19:45 UTC
Holder distribution
Holder distribution
Holder figures from the canonical report; observed 2026-10-18 19:45 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
0x05f04a08df246ce66d04b718c343f7190fe0848cFull creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2025-10-07 23:09 UTCToken launchedFirst on-chain trading pair opened on pancakeswap.
- 2026-10-18 19:45 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: High Risk (scanned 2026-10-18 19:45 UTC). The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable. 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 67,715 holders, largest measured holder 55.63% and top ten 71.49%. Holder observation: 2026-10-18 19:45 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.