BWC holder count
59Aug 24, 2026 10:00 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Current market check
BWC 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
BWC was archived on August 24, 2026 because 11 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · DueDWfgz6oGHaPgA8FUq6j3F3T7tSUtvyf1bBrW1pump
Latest dated evidence:
Follow the recorded trend
BWC price, market cap and trading activity
BWC has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
BWC top-holder concentration
99.45%Aug 24, 2026 10:00 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.BWC supply distribution
BWC chain snapshot: August 24, 2026. Account shares can include pools and custodians.
BWC: Largest measured entry
97.50%of recorded supply
BWC: Top ten measured entries
99.45%of recorded supply
BWC: Tracked deployer share
0.00%of recorded supply
The recorded sequence
What happened to BWC?
- 01First tracked
Entered the DexBrief catalog.
- 02Catalog retired
no tracked market after 11 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
BWC: what happened and what the record supports
What triggered the BWC retirement
For BWC, the stored decision is "no tracked market after 11 checks". The record counts 11 checks, but does not retain 11 independent provider responses. It cannot establish the date of BWC's last trade.
BWC ownership at the last saved chain check
The August 24, 2026 BWC snapshot records 59 measured holder entries through getProgramAccounts. It separately reports 367 token accounts; that account count is not a count of unique owners. 33 entries exceeded 0.01% of BWC supply. That is 55.9% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 99.45% of supply in that snapshot. The BWC concentration figure does not identify which large entries belong to pools, custodians or individual people.
BWC supply and contract controls
BWC's August 24, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 757,664,152.1894. The tracked deployer held 0.0000% of BWC supply at that check. A zero BWC balance does not show when or how those tokens left that address. The saved creator profile lists 701 mint(s) and 166 migration(s).
The missing interval in BWC's history
The BWC 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 20, 2026; catalog retirement is August 24, 2026. An observed decline between those markers cannot be reconstructed from the retained BWC 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-24 10:00 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
Download and cite this report
DexBrief. “BWC: retirement and market activity report.” Evidence checked 2026-08-24T10:00:36+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/bwc-7cac4629c080f8c5e55f/
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: 57e1aa3e8bb995b57df49b00e49c74575ca516729cb833c956551ac52f42a3b6