Bonsai$BONSAI
Risk analysis for Bonsai (BONSAI) on Ethereum — contract 0xc4954b16923d60f4114d289a8c989dfd4cadc32c. 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.
Price chart
Live price chart for BONSAI is provided by DexScreener.
Market overview
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
0x0Ac73242261A50e067f8263B9C4eDF5593bd306FThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Bonsai?
Bonsai ($BONSAI) is a ERC-20 token on the Ethereum blockchain Its primary trading venue is uniswap, with roughly $20.00K in live on-chain liquidity. It currently has 124 on-chain holders, and was first traded 10 days old. Rug.Tools' current assessment of Bonsai is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
Bonsai (BONSAI) is a Ethereum token analyzed by Rug.Tools. Current status: Multiple health signals are weakening, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 59.5% of supply, but independent wallet linkage is not fully corroborated.. Snapshot: ~$19,997 in on-chain liquidity, 124 holders, 6 days old. This page auto-updates as new on-chain data is collected.
Rug.Tools signals
Key statistics
Rug.Tools analysis
Multiple health signals are weakening, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 59.5% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot 1bf1366d · v3 · scanned 2026-10-01 05:41 UTC · page content updated 2026-10-01 05:41 UTC
Holder distribution
Creator profile
0x4bb7833ccf8d4d34f3ee8e5dc460ea5b13f794d4Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2026-09-24 19:42 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-10-01 05:41 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Compared using stored market cap, launch age and trading venue. Similarity is not a safety rating.
Finding comparable tokens…
Learn more
Frequently asked questions
What is Bonsai?⌄
Bonsai is a Ethereum 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 Bonsai safe?⌄
Current Rug.Tools verdict: Elevated Risk. Multiple health signals are weakening, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 59.5% 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 Bonsai have?⌄
Rug.Tools currently sees 124 holders. The top individual wallet holds 2.34% of supply; the top 10 individual wallets together hold 14.52%.
Where is Bonsai traded?⌄
The primary trading venue detected on Ethereum is uniswap. 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.