VeilPay
Risk analysis for VeilPay (VeilPay) on Solana — contract ETneXyW9cy26bqTQ2Y38Nj6JUfKmzM4pwwqi2VeDpump. 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 $VeilPay
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 VeilPay here
Solana snapshot
More details⌄
Price chart
Live price chart for VeilPay is provided by DexScreener.
Market overview
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
HRgttKGffKurPHEoRDguCeis4piS9gXkqe5sxZVcXshhThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is VeilPay?
VeilPay ($VeilPay) is a SPL token on the Solana blockchain Its primary trading venue is pumpswap, with roughly $16.53K in live on-chain liquidity. It currently has 383 on-chain holders, and was first traded 3 days old. Rug.Tools' current assessment of VeilPay is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
VeilPay is a Solana token analyzed by Rug.Tools. Current status: The token is actively trading, but the top 10 wallets hold 21.6% of supply, and liquidity is relatively low, so expect slippage when trading.. Snapshot: ~$16,529 in on-chain liquidity, 383 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 21.6% of supply, and liquidity is relatively low, so expect slippage when trading, and well-corroborated coordinated launch wallets acquired 11.7% of supply at launch.
Verdict from canonical snapshot 0f5daf70 · v3 · scanned 2026-10-01 04:42 UTC · page content updated 2026-09-30 08:07 UTC
Holder distribution
Creator profile
CpgYVsW5W4C5wEbHJwWBBVoqFrYDVsHVN9dDw6ek3UDZToken activity
- 2026-09-30 08:02 UTCToken launchedFirst on-chain trading pair opened on pumpswap.
- 2026-09-30 08:07 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Loading similar Solana tokens…
Learn more
Frequently asked questions
What is VeilPay?⌄
VeilPay 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 VeilPay safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but the top 10 wallets hold 21.6% of supply, and liquidity is relatively low, so expect slippage when trading, and well-corroborated coordinated launch wallets acquired 11.7% of supply at launch. 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 VeilPay have?⌄
Rug.Tools currently sees 383 holders. The top individual wallet holds 2.90% of supply; the top 10 individual wallets together hold 21.61%.
Where is VeilPay 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.