RAM
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
At launch
| Created | 2026-10-01 23:33 UTC |
| Creator | E4FPggw9yDp9PNJDuRoLYDr6a5HKCsAterw3fygLpZEA |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | 1 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | 3SffEZZi8zn39pTXGZscMx… slot 452,436,329
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-10-01 23:33:34 UTC Slot 452,436,329, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-01 23:34:09 UTC +35s Confirmed against the venue's own completion state. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | On 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 275 launches from 195 creator wallets, including this one. See them → |
| This creator | 1,072 earlier launches, 60 confirmed graduated on chain, 2 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 342 other creator wallets, across 660 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Random Access Meowry |
| Description | - |
| Metadata held | sha256 602e6507027ba2d00d043b45af0538862182205cbab34e9b93a598b08bd35672 · 382 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Picture held | sha256 b8515d9a9f984caf7bfbbe2eed076d6b63e93ad51f9f1f1cf2c27e160e118092 · 359,060 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 23:33 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.