JEMETHI holder count
20Sep 06, 2026 18:36 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.
Jemethi the rakoon was archived on September 06, 2026 because 3 catalog lookup checks did not retain a qualifying market for its Solana contract.
Solana · ELXA5F3GBWvo4ineD2wfDoUB1KLv4jbxKavQ7nMYV8v2
Latest dated evidence:
JEMETHI has 1 dated snapshots and 0 daily candles in this archive. Explore each available source and pool below.
Sep 06, 2026 18:36 UTC · One recorded value
getProgramAccounts · holder_count_measured · getProgramAccounts. More dated values are needed to chart a trend.Sep 06, 2026 18:36 UTC · One recorded value
getProgramAccounts · measured_top10_pct · getProgramAccounts. More dated values are needed to chart a trend.JEMETHI chain snapshot: September 06, 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 JEMETHI, 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 JEMETHI's last trade.
Jemethi the rakoon's saved token page retained price $0.00000221, 24-hour volume $2.53, fully diluted value $2.21K, 24-hour trades 3. Those fields lack a complete set of trustworthy observation dates, so they describe the archived JEMETHI snapshot and are excluded from dated return calculations. The saved route is a5e8orinjfK1jNHqTsvHsESqN8NJpC42rsnW8xysMRN. The $2.21K figure is fully diluted value; a circulating market cap was not retained for JEMETHI.
The September 06, 2026 JEMETHI snapshot records 20 measured holder entries through getProgramAccounts. It separately reports 76 token accounts; that account count is not a count of unique owners. 10 entries exceeded 0.01% of JEMETHI supply. That is 50.0% of the measured holder entries; the remainder held smaller balances. The measured top-ten entries represented 99.99% of supply in that snapshot. The JEMETHI concentration figure does not identify which large entries belong to pools, custodians or individual people.
Jemethi the rakoon's September 06, 2026 contract snapshot records mint authority: revoked; freeze authority: revoked; token supply: 999,788,109.4628. The tracked deployer held 0.0000% of JEMETHI supply at that check. A zero JEMETHI balance does not show when or how those tokens left that address. The saved creator profile lists 1 mint(s).
The JEMETHI 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 06, 2026. An observed decline between those markers cannot be reconstructed from the retained JEMETHI 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-06 18:36 UTC | getProgramAccounts | getProgramAccounts | Not recorded | Not recorded | Not recorded | Not recorded |
DexBrief. “Jemethi the rakoon: retirement and market activity report.” Evidence checked 2026-09-06T18:36:33+00:00. Methodology 2.1. https://dexbrief.com/graveyard/reports/jemethi-99de3679f1263c96f3f0/
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: 48c3670511a4d9d4efb5c6ef06a6f9c42b9e97f18ff8c371f1f7766305d7e475