SHIBABUTT holder count
119Aug 18, 2026 19:23 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.
Shibabutt was archived on July 21, 2026 because 3 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · DiyUY3XkEG8ZBjoiX9i38oFHmjToCnTZFYNWJqxBpump
Latest dated evidence:
SHIBABUTT has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
Aug 18, 2026 19:23 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Aug 18, 2026 19:23 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.SHIBABUTT chain snapshot: August 18, 2026. Account shares can include pools and custodians.
Entered the DexBrief catalog.
no tracked market after 3 checks
First tracked is not launch; retirement is a catalog decision, not a verified final trade or cause of death.
For SHIBABUTT, the stored decision is "no tracked market after 3 checks". The record counts 3 checks, but does not retain 3 independent provider responses. It cannot establish the date of SHIBABUTT's last trade.
Shibabutt's saved token page retained price $0.00000164, 24-hour volume $0.17, pool liquidity $3.11K, fully diluted value $1.64K, 24-hour trades 1. Those fields lack a complete set of trustworthy observation dates, so they describe the archived SHIBABUTT snapshot and are excluded from dated return calculations. The saved route is 4kNK7MsufgqiLEVzymEU6xi8NynQpEhWtatGRhzKQ7R5. The $1.64K figure is fully diluted value; a circulating market cap was not retained for SHIBABUTT.
The August 18, 2026 SHIBABUTT snapshot records 119 measured holder entries through getProgramAccounts. It separately reports 867 token accounts; that account count is not a count of unique owners. 37 entries exceeded 0.01% of SHIBABUTT supply. That is 31.1% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 98.59% of supply in that snapshot. The SHIBABUTT concentration figure does not identify which large entries belong to pools, custodians or individual people.
Shibabutt's August 18, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 998,106,477.8118. The tracked deployer held 0.0000% of SHIBABUTT supply at that check. A zero SHIBABUTT 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 SHIBABUTT 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 25, 2026; catalog retirement is July 21, 2026. An observed decline between those markers cannot be reconstructed from the retained SHIBABUTT 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-08-18 19:23 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
DexBrief. “Shibabutt: retirement and market activity report.” Evidence checked 2026-08-18T19:23:40+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/shibabutt-39e2c467b08bd7b79243/
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: 4478c77b3a1e76407357b40269c29306dabbe04245094559a658359d2f7c739a