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