Kim Hyunsik$김현식
Risk analysis for Kim Hyunsik (김현식) on BNB Chain — contract 0x16d668187d7aab2219fe55ddf862622bd1c47777. 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 provider unavailable — showing last verified values from 8 hours ago.
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
0x61D6562714698c630fb98B44Fd36C792dA5F0426The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Kim Hyunsik?
Kim Hyunsik ($김현식) is a BEP-20 token on the BNB Chain blockchain Its primary trading venue is pancakeswap, with roughly $21.38K in live on-chain liquidity. It currently has 436 on-chain holders, and was first traded new (today). Rug.Tools' current assessment of Kim Hyunsik is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
Kim Hyunsik (김현식) is a BNB Chain token analyzed by Rug.Tools. Current status: The token is actively trading, but liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 21.2% of supply, but independent wallet linkage is not fully corroborated.. Snapshot: ~$21,382 in on-chain liquidity, 436 holders. 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 liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 21.2% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot 7004191f · v3 · scanned 2026-10-03 10:16 UTC · page content updated 2026-10-03 10:16 UTC
Holder distribution
Creator profile
0x7c85eaea2098ae2619555f609b1b2e3101292587Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2026-10-03 09:34 UTCToken launchedFirst on-chain trading pair opened on pancakeswap.
- 2026-10-03 10:16 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Loading similar BNB Chain tokens…
Learn more
Frequently asked questions
What is Kim Hyunsik?⌄
Kim Hyunsik 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 Kim Hyunsik safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 21.2% 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 Kim Hyunsik have?⌄
Rug.Tools currently sees 436 holders. The top individual wallet holds 2.09% of supply; the top 10 individual wallets together hold 11.46%.
Where is Kim Hyunsik 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.