OZZIE
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 19:29 UTC |
| Creator | FxnUuCWgg2YkHSnqJCmZiU12VU7T4Z66x6kp91XaoqwY |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 23 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 1 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | yes |
| Recorded from | 5Eibyeq5EgABYUonqRWvYu… slot 452,704,620
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 19:29:36 UTC Slot 452,704,620, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-10-02 19:29:50 UTC +15s
4.935e-8 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 10 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
| Curve completed | 2026-10-02 19:34:54 UTC +5m 18s Confirmed: a PumpSwap pool was found for it. |
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 3 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 7 launches from 5 creator wallets, including this one. See them → |
| This creator | 77 earlier launches, 1 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 12 other creator wallets, across 27 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
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-03 02:08 UTC, just now |
What this launch claimed to be
| Name | OZZIE |
| Metadata held | sha256 76a1ffd7ec1e2bfd17853f6a8870b1278d36b1a4dfa65cb7975b9e87bd250fba · 292 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 1372ab4f80912f2e0cb5a13d8fdeda38dc1d061460a8b9451099d4fce4baf800 · 299,144 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 19:29 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.