Price chart
What is bajiecat?
bajiecat ($bajie) is a SPL token on the Solana blockchain Its primary trading venue is pumpfun. It currently has 80 on-chain holders, and was first traded 5 days old. Rug.Tools' current assessment of bajiecat is "Healthy Project", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
bajiecat (bajie) is a Solana token analyzed by Rug.Tools. Current status: The token is actively trading with no major on-chain risks detected.. Snapshot: 80 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 with no major on-chain risks detected.
Last analyzed 7/26/2026, 4:08:48 PM
Holder distribution
Creator profile
4sfQe3f7nwa5Y4zYyCoU7CKJqkyADg1meaAQYtPdw6sXToken activity
- 7/26/2026, 3:28:06 PMToken launchedFirst on-chain trading pair opened on pumpfun.
- 7/26/2026, 4:08:48 PMRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Loading similar Solana tokens…
Learn more
Frequently asked questions
What is bajiecat?⌄
bajiecat 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 bajiecat safe?⌄
Current Rug.Tools verdict: Healthy Project. The token is actively trading with no major on-chain risks detected. 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 bajiecat have?⌄
Rug.Tools currently sees 80 holders. The top individual wallet holds 3.05% of supply; the top 10 individual wallets together hold 22.34%.
Where is bajiecat traded?⌄
The primary trading venue detected on Solana is pumpfun. Use the "Trade" button above to open the pair on DexScreener.
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.