BREW holder count
27Aug 25, 2026 12:29 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Current market check
BREW market now
PriceUnavailable
Market capUnavailable
24h trading volumeUnavailable
Pool liquidityUnavailable
Saved market observation: Not recorded. Refreshes when you visit.
·
Current quotes are separate from the historical report below. Volume and liquidity describe the displayed pool; unavailable fields are not zero.
The finding
Contract-specific market history
BREW was archived on August 25, 2026 because 3 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · eaziad4RzM4oVxQcYg3RK8xV7NHkJwZXFv1mrBXbrew
Latest dated evidence:
Follow the recorded trend
BREW price, market cap and trading activity
BREW has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
BREW top-holder concentration
99.84%Aug 25, 2026 12:29 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.BREW supply distribution
BREW chain snapshot: August 25, 2026. Account shares can include pools and custodians.
BREW: Largest measured entry
92.79%of recorded supply
BREW: Top ten measured entries
99.84%of recorded supply
BREW: Tracked deployer share
0.00%of recorded supply
The recorded sequence
What happened to BREW?
- 01First tracked
Entered the DexBrief catalog.
- 02Catalog retired
no tracked market after 3 checks
First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.
The evidence in this case
BREW: what happened and what the record supports
What triggered the BREW retirement
For BREW, 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 BREW's last trade.
BREW ownership at the last saved chain check
The August 25, 2026 BREW snapshot records 27 measured holder entries through getProgramAccounts. It separately reports 153 token accounts; that account count is not a count of unique owners. 19 entries exceeded 0.01% of BREW supply. That is 70.4% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 99.84% of supply in that snapshot. The BREW concentration figure does not identify which large entries belong to pools, custodians or individual people.
BREW supply and contract controls
BREW's August 25, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 999,804,439.5656. The tracked deployer held 0.0000% of BREW supply at that check. A zero BREW balance does not show when or how those tokens left that address. The saved creator profile lists 1 mint(s) and 1 migration(s).
The missing interval in BREW's history
The BREW 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 June 22, 2026; catalog retirement is August 25, 2026. An observed decline between those markers cannot be reconstructed from the retained BREW values alone.
Provider checks & full observation table
Latest provider checks
| Source | Result | Checked (UTC) | Pools returned | Evidence |
|---|
Recorded market evidence
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-08-25 12:29 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
Download and cite this report
DexBrief. “BREW: retirement and market activity report.” Evidence checked 2026-08-25T12:29:16+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/brew-f0761adc89f5341a6352/
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.
Evidence SHA-256: 4eb79d2580f77fbd3b45c411551caac2bf0d9178828a1c2c3cff424a7e587a4c