JUICEMAN has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
JUICEMAN holder count
833
Sep 01, 2026 12:53 UTC · One recorded value
public Robinhood Chain RPC + contract-bound Blockscout/GeckoTerminal · holder_count · public Robinhood Chain RPC + contract-bound Blockscout/GeckoTerminal. More dated values are needed to chart a trend.
JUICEMAN top-holder concentration
63.46%
Sep 01, 2026 12:53 UTC · One recorded value
public Robinhood Chain RPC + contract-bound Blockscout/GeckoTerminal · top_holders_pct · public Robinhood Chain RPC + contract-bound Blockscout/GeckoTerminal. More dated values are needed to chart a trend.
The recorded sequence
What happened to JUICEMAN?
01First tracked
Entered the DexBrief catalog.
02Catalog retired
no tracked market after 3 checks
03Follow-up check
No market returned by the checked sources
First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.
The evidence in this case
JUICEMAN: what happened and what the record supports
What triggered the JUICEMAN retirement
For JUICEMAN, the stored decision is "no tracked market after 3 checks". The record counts 3 checks, but does not retain 3 independent provider responses. It cannot establish the date of JUICEMAN's last trade.
The saved market footprint of JUICEMAN
Juiceman by Virtuals's saved token page retained price $0.00004485, 24-hour volume $93.99K, pool liquidity $35.83K, fully diluted value $44.85K, 24-hour trades 357. Those fields lack a complete set of trustworthy observation dates, so they describe the archived JUICEMAN snapshot and are excluded from dated return calculations. The saved route is 0x53a8fe1482ef31e96c94cebaef8bbf76808bfcaf. The $44.85K figure is fully diluted value; a circulating market cap was not retained for JUICEMAN.
JUICEMAN ownership at the last saved chain check
The September 01, 2026 JUICEMAN snapshot records 833 reported holders through public Robinhood Chain RPC + contract-bound Blockscout/GeckoTerminal. The provider top-holder group represented 63.46% of supply in that snapshot. The JUICEMAN concentration figure does not identify which large entries belong to pools, custodians or individual people.
JUICEMAN supply and contract controls
Juiceman by Virtuals's September 01, 2026 contract snapshot records contract ownership: none; token supply: 1,000,000,000.
What the later JUICEMAN lookup returned
At the September 17, 2026 follow-up for JUICEMAN, the results were DexScreener: empty; GeckoTerminal: empty. No matching JUICEMAN market was returned by these completed checks.
The missing interval in JUICEMAN's history
The JUICEMAN archive currently contains 1 dated snapshot(s) and 0 daily candle(s). It lacks a comparable price or activity series spanning at least six hours. First tracking is July 22, 2026; catalog retirement is August 01, 2026. An observed decline between those markers cannot be reconstructed from the retained JUICEMAN values alone.
Each row is one source and one scope. Pool liquidity and activity are not token-wide totals. Missing fields are not zero. Full history is available in the downloads.
Observed (UTC)
Source
Scope / exact pool
Price
Liquidity
24h volume
24h trades
2026-09-01 12:53 UTC
public Robinhood Chain RPC + contract-bound Blockscout/GeckoTerminal
public Robinhood Chain RPC + contract-bound Blockscout/GeckoTerminal
Not recorded
Not recorded
Not recorded
Not recorded
Download and cite this report
DexBrief. “Juiceman by Virtuals: retirement and market activity report.” Evidence checked 2026-09-17T00:10:55+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/juiceman-55ebce68b1e27875b8f7/
DexBrief’s compiled observations and analysis may be cited with attribution under CC BY 4.0; underlying provider data remains subject to its source terms.