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