Token report · Avalanche
DizzyHavoc (DZHV)
Live risk score, status, liquidity and trading activity for the DizzyHavoc token address on Avalanche.
- Price
- $0.0003137
- Liquidity
- 24.71K
- 24h volume
- 4.52K
- 24h txns
- 18
- FDV
- 99.08K
- Last seen
- 20h ago A few hours old
Risk score
Main signal: Low liquidity
Based on the latest market snapshot. Lower is better. It reacts to liquidity, trading activity, volume, valuation and detected red flags.
Health score
Low liquidity, low volume, or thin transaction flow make this token fragile right now. Uses the latest liquidity, 24h volume, 24h transactions, token age and the current risk score.
Quick verdict
Needs confirmation
There is some activity here, but not enough strength to trust the setup without extra checks on liquidity, volume, and recent status changes.
- Most important signal
- Low liquidity
- Best next step
- Open the explorer and verify the contract
Check next
- Liquidity is thinWait for deeper liquidity before trusting price action. Thin pools can move violently and are easier to manipulate.
- Trading activity is still weakCheck whether buys, sells, and unique transactions keep building. A token with weak flow can fade quickly after first attention.
- Review the flagged risk signalsWe detected: low liquidity. Open the explorer and the pair page before assuming the setup is clean.
- Status already slipped to warningThis token has already weakened from a cleaner state. Compare the trend and current volume before treating dips as opportunity.
Summary and red flags
DizzyHavoc (DZHV) is a 964d old token on AVALANCHE with token address 0x3419875B4D3Bca7F3FddA2dB7a476A79fD31B4fE, risk score 50, and warning status. FreshTokenWatch currently tracks 18 recorded 24h transactions, liquidity around $24.7K, and 24h volume near $4.5K.
- Low liquidity
- Low 24h trading volume
Risk trend
How the risk score changed across recent snapshots (Apr 2, 2026, 5:45 AM to Oct 18, 2026, 9:14 AM (90 recorded snapshots)). Not a price chart.
Dots: green active, yellow warning, red dead.
Live pair chart
Token details
- Token address
- 0x341987…fD31B4fE
- Chain
- Avalanche
- Status
- Warning
- Pair created
- Feb 27, 2024, 12:27 AM
- Listed on FreshTokenWatch
- Apr 1, 2026, 7:49 AM
- Data source
- DEX market data
- FDV / liquidity
- 4.01x
- Record updated
- 20h ago
Trading pools
Related tokens
| Token | Age | Liquidity | 24h Vol | Risk | Summary |
|---|---|---|---|---|---|
| 5mo | 38.88K | 17.73K | 50Med | $17.73KLiq 38.88K50 | |
| 2y | 24.96K | 7.84K | 68Med | $7.84KLiq 24.96K68 | |
| 4y | 492.01K | 7.76K | 48Med | $7.76KLiq 492.01K48 | |
| 2y | 25.6K | 7.13K | 50Med | $7.13KLiq 25.6K50 | |
| 2y | 524.65K | 2.51K | 53Med | $2.51KLiq 524.65K53 | |
 ORNGOrange | 2y | 16.61K | 1.84K | 68Med | $1.84KLiq 16.61K68 |
| 1y | 170.42K | 1.8K | 56Med | $1.8KLiq 170.42K56 | |
| 6mo | 10.02K | 1.79K | 62Med | $1.79KLiq 10.02K62 |
Learn these checks
- Token AddressUsing the wrong token address is one of the fastest ways to buy the wrong asset or a copycat contract.
- Risk ScoreIt helps prioritize review, but is not investment advice.
- Trading VolumeVolume helps distinguish real market interest from inactive or abandoned pairs, though it can still be manipulated.
- Liquidity PoolPool depth affects slippage, execution quality, and whether a token has a real market at all.
- Liquidity LockA lock is a positive signal, but not a full security guarantee.
Token FAQ
What is the DZHV token address on Avalanche?
The tracked DZHV token address on Avalanche is 0x3419875B4D3Bca7F3FddA2dB7a476A79fD31B4fE. FreshTokenWatch shows the exact contract address in the page content so users can verify they are looking at the right token.
Is DZHV on Avalanche safe?
DZHV currently has a FreshTokenWatch risk score of 50/100 and a warning status. That is not an endorsement or a guarantee. It is a live scanner snapshot based on liquidity, volume, activity, valuation balance, and current red flags. The main concern right now is low liquidity
How should I verify the DZHV contract before trading?
Verify the token address 0x3419875B4D3Bca7F3FddA2dB7a476A79fD31B4fE, compare the token against the scanner history, review liquidity and 24h transaction activity, and open the external explorer or DEX pair pages before acting.