Every "my swap is stuck / slow / pending / failed" case on Solana comes down to a handful of causes. This page covers each one, what it looks like, and the fix. It applies to any token — memecoins, majors and stables behave the same at the transaction layer.
A Solana transaction references a recent blockhash that expires after roughly 60–90 seconds. If your transaction isn't included in a block before that window closes, it doesn't sit in a queue — it simply expires and can never land. A wallet that still shows "pending" after two minutes is showing you a transaction that is already dead. The fix is to re-submit the swap; nothing was spent, because a transaction that never landed never executed. On Verixia, quotes re-lock automatically when you retry.
During congestion (a hyped launch, an NFT mint, a volatile hour) validators prioritize transactions carrying higher priority fees. A swap sent with a low fee can take many blocks to land or expire outright. Verixia routes sends through an RPC configured for MEV-protected delivery with a sane priority fee, which is why the typical swap settles in under a second even in busy periods. If you're using your own tooling, raise the priority fee before resubmitting.
Between quoting and executing, the pool moved more than your slippage setting allows, so the program aborted rather than fill you at a worse price. This is protection working, not an error. On thin pools a 1% move between quote and execution is common. Either accept a slightly higher slippage, trade a smaller size (less price impact per fill), or wait for calmer flow. See the slippage guide for how to pick a safe setting.
Price impact is a function of your order size against pool depth. A $500 order into a pool holding $20K of liquidity will move the price several percent no matter which app routes it. Check the token's total liquidity before sizing an order — Verixia surfaces per-venue depth on every token page, and the Token Risk Hub flags thin-liquidity tokens before you commit. If impact looks absurd (20%+), the pool is nearly empty or the route is crossing several hops; split the trade or reconsider.
Two wallet problems masquerade as swap failures. First, insufficient SOL for fees and rent: keep at least ~0.01 SOL beyond the amount you're swapping. Second, a stale cached app version: hard-refresh the page. Verixia no longer uses a service worker, so a single refresh always loads the current build.
Retry an expired swap rather than waiting on it; raise priority fees during congestion; treat slippage aborts as protection and adjust size before adjusting tolerance; check pool depth before large orders; keep spare SOL for fees. If a specific token keeps failing while others work, run it through a token risk check — transfer taxes, freeze authority and sell restrictions produce exactly this pattern.