Verify every token before you buy Unlimited checks · $3.99/wk · Cancel anytime
Get Unlimited
Swap on Verixia
[ on-chain  ·  solana + evm ]

Rug Pull Risk Check

Review the liquidity lock status, holder concentration, and contract permissions before committing to a position.

Read the contract before the contract reads you. Honeypot, rug, and scam detection from on-chain state — not market data.

⚠️ Token Risk Check
✓ On-Chain Analysis
🔒 No Signup
⚡ Results in Seconds
🔍 Honeypot detection
💧 LP lock status
👥 Holder concentration
⚡ Solana + EVM
4.6 / 5 from 2,066 users Direct on-chain reads 🔐 Non-custodial — no wallet connect required Sub-5-second scan 🔗 Solana · Ethereum · Base · Arbitrum · BNB · Polygon · Avalanche 📊 64,552 risk checks run
Live
🔍 On-chain read ⚡ Seconds ✓ No signup
>_
Enter the full token contract address for the most accurate on-chain analysis
No address? Try a popular check:
1 free check · Unlimited from $3.99/wk
No signup required · Results in seconds
Unlimited checks from $3.99 / week · Cancel anytime
Use the same email entered during checkout to restore access
Unlimited token checks active

Unlimited Token Risk Checks

Verify every contract before buying. Honeypot detection, LP lock analysis, and holder concentration reviews across Solana and EVM.
$5.6BFBI crypto losses 2023
$1B+FTC losses 2023
<5sper contract scan
Best Value -- Save 80%
Yearly Access
$39.99 / yr  ·  $3.33/mo
Popular
Monthly Access
$11.99 / month
Try it -- no commitment
Weekly Access
$3.99 / week · cancel anytime
SSL Secured Stripe Cancel anytime No hidden fees
Live Detections
127 scans today
49K+Scans Run
6Chains
15+Risk Signals
FreeFirst Check
What the checker detects
Example signals · run a scan to see live results
⚠️Sell TaxDETECTED
💧LP LockUNLOCKED
🔑Mint AuthorityACTIVE
OwnershipRENOUNCED
🐋Whale Wallet42%
📅Token Age3 DAYS
🚨Approval RiskHIGH
CooldownACTIVE
🔄Last Update48H AGO
📉Liquidity 24h-12%
🚫Transfer LockENCODED
Freeze AuthENABLED
📋ContractVERIFIED
💰LP Depth$48K
🔗Blacklist FnPRESENT
🔍
Honeypot Detection
Simulates sell transactions to detect transfer locks, fee traps, and whitelist-only exit conditions before you buy in. Reads the contract directly — not market data. Works across Solana SPL tokens and all major EVM chains.
💧
Liquidity & Holders
Reviews pool depth, LP lock status, and top wallet percentages. Surfaces unlocked pools and concentrated wallets before the price collapses.
Results in Seconds
On-chain read — no API delays, no market data lag. Raw contract analysis returned in under 5 seconds.
Token verified? Swap at best price.
Route across Raydium, Orca, Meteora & 50+ DEXes — non-custodial, no KYC
Swap on Verixia →
SOL ETH BASE ARB BNB AVAX Powered by Verixia

Token Risk Analysis -- Contract, Liquidity & Holders

🔗 TL;DR

A token's risk lives in three places: contract permissions (can the dev mint, freeze, or block sells?), liquidity structure (is the LP locked and deep enough to exit?), and holder distribution (can a handful of wallets dump the entire float?). The checker above reads all three directly on-chain in under five seconds.

Scan time< 5 sec
Signals checked15+
Cost (first check)Free

Ethereum contracts that exhibit structural patterns indicative of rug pull risk often incorporate mechanisms that restrict token transfers, effectively trapping holders and preventing them from exiting their positions freely. Among the most scrutinized patterns is the presence of whitelist-only exit mechanics embedded directly into the token’s transfer function. This design typically requires that only addresses explicitly approved by the contract owner can initiate sell or transfer operations. Technically, this is enforced through conditional statements—such as require() checks—or mapping structures that revert any token movement attempts by non-whitelisted wallets. While this pattern can allow buy transactions to proceed unhindered, thereby maintaining an appearance of liquidity and tradability, it effectively blocks a significant portion of holders from selling, which can be a critical component of a rug pull scheme.

The significance of whitelist-only exit patterns in assessing risk hinges primarily on the degree of owner control and the transparency surrounding the whitelist’s management. If the whitelist is immutable, fixed at launch, and publicly verifiable, this pattern might serve legitimate purposes. These can include regulatory compliance, staged token releases, or vesting schedules designed to prevent market flooding. In these cases, the whitelist acts as a controlled gateway to orderly market participation. However, if the contract owner retains the ability to modify the whitelist dynamically after deployment, this introduces an ongoing latent risk. In such scenarios, the owner can selectively restrict selling privileges at any moment, effectively locking in holders and setting the stage for a rug pull. It is important to note that the mere existence of a whitelist mechanism does not inherently confirm malicious intent; some projects employ these controls with genuine operational justifications. Still, when combined with a lack of clear communication or rationale, owner mutability significantly elevates the risk profile.

Beyond whitelist-only exit mechanics, other contract-level features can compound rug pull risks. Adjustable sell taxes controlled by the owner are a notable example. These taxes, if modifiable post-deployment, can act as soft honeypots. Unlike outright blocking sells, they impose financial penalties on sellers, potentially deterring exit attempts by making them economically unviable. This subtle discouragement can be more insidious, as it does not halt sales outright but can still lead to liquidity traps under certain market conditions. Similarly, active mint authority—where the contract owner can create new tokens at will—introduces dilution risks that can erode holder value and precipitate price crashes. While minting can serve legitimate purposes such as inflationary rewards or liquidity incentives, the absence of renouncement or transparent governance around minting expands the potential for abuse.

Mitigating factors are equally important to assess. Multisignature (multisig) controls or timelocks on critical owner functions can substantially limit unilateral action, reducing the likelihood that a single actor can manipulate whitelist entries, sell taxes, or minting capabilities arbitrarily. Transparent governance frameworks that involve community oversight or scheduled updates also provide safeguards against sudden, covert changes that harm holders. On-chain transaction history offers additional context; if no evidence exists of blacklist activations, freeze functions, or punitive tax increases, the immediate risk is less pronounced. However, the structural capability remains a latent factor, as these features can be activated without warning.

Liquidity considerations further deepen the analysis. Whitelist restrictions or sell penalties paired with thin liquidity pools—those with depths under $50,000, for instance—can exacerbate the effects of exit controls. In such environments, even small permitted sell orders can cause outsized price slippage, discouraging transactions and amplifying losses. For holders blocked from selling, the result is effectively a forced illiquidity condition, trapping capital as market value deteriorates. When these dynamics unfold in tokens with low market capitalization, typically under several million dollars, the vulnerability intensifies. Price manipulation and panic selling become more feasible, and recovery becomes increasingly difficult. Conversely, projects with deep liquidity pools—well above median depths—and active, decentralized trading networks tend to absorb sell pressure more effectively, thereby dampening the impact of restrictive contract features.

It is crucial to emphasize that none of these patterns alone definitively confirm malicious intent or guarantee a rug pull. A whitelist-only exit feature can sometimes be part of a legitimate tokenomics strategy, and adjustable taxes or minting rights may be designed for adaptive operational reasons. The risk emerges primarily when these features intersect with opaque ownership, lack of governance safeguards, thin liquidity, and low capitalization. In such cases, the structural design facilitates conditions where holders can be trapped and liquidity drained. These layered risks demand careful consideration, as their interplay shapes the real-world outcomes for investors and traders navigating Ethereum-based tokens.

Pre-buy on-chain checklist

  • Mint authority renouncedConfirms supply is capped — no new tokens can be issued post-launch.
  • LP locked or burnedLiquidity cannot be removed in a single transaction. Lock duration and locker contract are both verifiable on-chain.
  • !Top 10 holders under 40%Lower concentration means coordinated dumps are mechanically harder. Above 40% is a structural caution.
  • !No active freeze authorityActive freeze means wallets can be paused at the contract level — no exit possible during a freeze.
  • ×No transfer restrictionsThe transfer function should accept any holder selling. Encoded sell blocks, whitelist exits, and hidden tax functions are honeypot signatures.

Frequently asked questions

Verify the contract address before you buy in. Paste it into the scanner above for the full on-chain breakdown.

Why on-chain signals matter

🔒
Non-custodial Your wallet keys never leave your device. Funds move directly between wallets through the smart contract — Verixia holds nothing.
No account required No sign-up, no KYC, no email. Connect your wallet and swap. Disconnect at any time — no ongoing permissions required.
Solana + EVM Checks SPL tokens and EVM contracts across Ethereum, Base, Arbitrum, BNB Chain, Polygon, and Avalanche.
⚙ Methodology
Every risk verdict is generated from three on-chain reads run in parallel: (1) direct contract bytecode analysis for honeypot patterns, mint/freeze authority, and blacklist functions; (2) liquidity pool inspection for LP lock status, depth, and removable percentage; (3) holder distribution from token-account snapshots. No editorial opinion is layered on the output. Read the full methodology →