DAY holder count
55Aug 25, 2026 12:13 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Current market check
DAY 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
DAY was archived on August 25, 2026 because 19 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · DAYsmmxaDNAbn6cCotvRczSn1o1ySuwRRgkq7f1TKVHt
Latest dated evidence:
Follow the recorded trend
DAY price, market cap and trading activity
DAY has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
DAY top-holder concentration
99.85%Aug 25, 2026 12:13 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.DAY supply distribution
DAY chain snapshot: August 25, 2026. Account shares can include pools and custodians.
DAY: Largest measured entry
98.16%of recorded supply
DAY: Top ten measured entries
99.85%of recorded supply
DAY: Tracked deployer share
0.00%of recorded supply
The recorded sequence
What happened to DAY?
- 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
DAY: what happened and what the record supports
What triggered the DAY retirement
For DAY, 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 DAY's last trade.
DAY ownership at the last saved chain check
The August 25, 2026 DAY snapshot records 55 measured holder entries through getProgramAccounts. It separately reports 372 token accounts; that account count is not a count of unique owners. 16 entries exceeded 0.01% of DAY supply. That is 29.1% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 99.85% of supply in that snapshot. The DAY concentration figure does not identify which large entries belong to pools, custodians or individual people.
DAY supply and contract controls
DAY's August 25, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 999,480,513.7879. The tracked deployer held 0.0000% of DAY supply at that check. A zero DAY balance does not show when or how those tokens left that address. The saved creator profile lists 6 mint(s) and 4 migration(s).
The missing interval in DAY's history
The DAY 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 11, 2026; catalog retirement is August 25, 2026. An observed decline between those markers cannot be reconstructed from the retained DAY 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:13 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
Download and cite this report
DexBrief. “DAY: retirement and market activity report.” Evidence checked 2026-08-25T12:13:17+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/day-1603877b790dce943e93/
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: 310c65c028345ef8ddb1ba7325d37ce73c064b87fd7e0358127602aba78f1469