DroneKiller$DKILL
Risk analysis for DroneKiller (DKILL) on Solana — contract H7kfBWQqs5asqvzynqRaS6h9jLFc9g1tDQYPnbDSpump. 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.
Buy & Sell $DKILL
Powered by Jupiter routingSwap without leaving Rug.Tools. Rug.Tools analyzes risk; it does not guarantee a token is safe. Review the quote and wallet approval before signing.
Rug.Tools Swap · Jupiter
Swap DKILL here
Solana snapshot
More details⌄
Price chart
Live price chart for DKILL is provided by DexScreener.
Market overview
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
9dufQSfLH84Eqan4TCmEPdW3wb1uh4qf3LrczzDfQPYPThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is DroneKiller?
DroneKiller ($DKILL) is a SPL token on the Solana blockchain Its primary trading venue is pumpswap, with roughly $27.91K in live on-chain liquidity. It currently has 391 on-chain holders, and was first traded 6 days old. Rug.Tools' current assessment of DroneKiller is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
DroneKiller (DKILL) is a Solana token analyzed by Rug.Tools. Current status: The token is actively trading, but the top 10 wallets hold 24.0% of supply, and a launch-pattern cluster acquired 38.8% of supply, but independent wallet linkage is not fully corroborated.. Snapshot: ~$27,906 in on-chain liquidity, 391 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 the top 10 wallets hold 24.0% of supply, and a launch-pattern cluster acquired 39.0% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot d7602193 · v3 · scanned 2026-09-28 07:25 UTC · page content updated 2026-09-27 03:11 UTC
Holder distribution
Creator profile
93bS8URCKjcFLabKCK6oQBsBkGmum2SFU9T5EXXyK23cToken activity
- 2026-09-27 02:44 UTCToken launchedFirst on-chain trading pair opened on pumpswap.
- 2026-09-27 03:11 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Loading similar Solana tokens…
Learn more
Frequently asked questions
What is DroneKiller?⌄
DroneKiller is a Solana 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 DroneKiller safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but the top 10 wallets hold 24.0% of supply, and a launch-pattern cluster acquired 39.0% 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 DroneKiller have?⌄
Rug.Tools currently sees 391 holders. The top individual wallet holds 3.58% of supply; the top 10 individual wallets together hold 24.01%.
Where is DroneKiller traded?⌄
The primary trading venue detected on Solana is pumpswap. 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.