STRONK holder count
14Sep 04, 2026 07:19 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Watchlist, recently viewed tokens, and since-last-visit snapshots follow this account. Nothing is emailed.
Solana · Follow-up pending
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.
STRONK was archived on September 04, 2026 because 2 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · FSnh2efmNgCwzJigpAgxhRr4F5hNUFGyDWMXrpJtpump
Latest dated evidence:
STRONK has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
Sep 04, 2026 07:19 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Sep 04, 2026 07:19 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.STRONK chain snapshot: September 04, 2026. Account shares can include pools and custodians.
Entered the DexBrief catalog.
no tracked market after 2 checks
First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.
For STRONK, the stored decision is "no tracked market after 2 checks". The record counts 2 checks, but does not retain 2 independent provider responses. It cannot establish the date of STRONK's last trade.
STRONK's saved token page retained price $0.00000213, 24-hour volume $6.78, fully diluted value $2.14K, 24-hour trades 2. Those fields lack a complete set of trustworthy observation dates, so they describe the archived STRONK snapshot and are excluded from dated return calculations. The saved route is 8xKCM15WABVnKSjgY9dm7Vap3vVStnZUaQ8F6trYagPE. The $2.14K figure is fully diluted value; a circulating market cap was not retained for STRONK.
The September 04, 2026 STRONK snapshot records 14 measured holder entries through getProgramAccounts. It separately reports 151 token accounts; that account count is not a count of unique owners. 9 entries exceeded 0.01% of STRONK supply. That is 64.3% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 99.99% of supply in that snapshot. The STRONK concentration figure does not identify which large entries belong to pools, custodians or individual people.
STRONK's September 04, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 999,499,173.7401. The tracked deployer held 0.0000% of STRONK supply at that check. A zero STRONK balance does not show when or how those tokens left that address. The saved creator profile lists 3,183 mint(s) and 144 migration(s).
The STRONK 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 18, 2026; catalog retirement is September 04, 2026. An observed decline between those markers cannot be reconstructed from the retained STRONK values alone.
| Source | Result | Checked (UTC) | Pools returned | 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-09-04 07:19 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
DexBrief. “STRONK: retirement and market activity report.” Evidence checked 2026-09-04T07:19:21+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/stronk-2a45fa3da715ebc007d8/
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: 4ad601f252888b9ed750a38570628da197aee033f6f7c9ad6b161fe8af23aabd