OUYS
The curve completed 7s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
findingIt left the curve 7s after launch.
noteOnly 2.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 23:18 UTC |
| Creator | 3R9YV47A8CUm1J8CNntxWgKaDM274bDDVTcTX6DzzJzK |
| Creator took | 3.0% of supply in the first block |
| Outside buyers | 129 distinct wallets, not counting the creator, bought on the bonding curve: 129 within the first 30s, 10 bundled into the creation block. |
| Graduated | 0 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 | not while we watched |
| Recorded from | 2e4ZXvu8mjSzEWRmRDVWJQ… slot 452,432,930
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 23:18:23 UTC Slot 452,432,930, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-01 23:18:30 UTC +7s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 23:18:30 UTC +7s
4.109e-7 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 | 129 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. |
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 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 2 launches from 2 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.5 SOL |
| Read from chain | 2026-10-02 04:56 UTC, just now |
What this launch claimed to be
| Name | Ouys |
| Description | Every 0.5 SOL in fees rips a real graded Pokémon pack live. Every SOL you buy in the round is a ticket for the card — drawn on-chain |
| Metadata held | sha256 d95564ff2cb234a91e497213a3388d1cb7c17d69dcfab4d5bd0b2f14e2e196ae · 383 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 5356243c07c5b97af3de4fc5121444e18e8f6ccea64629216d00983d009a4dbd · 1,032,281 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 23:18 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.