si16z
The curve completed 36s 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 36s after launch.
noteOnly 19.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 16:06 UTC |
| Creator | 2h5ZCrGTEj7UqBnQW6uPx9itHBryErD1j1Gj45Es9uLQ |
| Creator took | 5.1% of supply in the first block |
| Outside buyers | 238 distinct wallets, not counting the creator, bought on the bonding curve: 211 within the first 30s, 12 bundled into the creation block. |
| 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 while we watched |
| Recorded from | VVKjTT3dbifz6EL45EkTHE… slot 452,013,464
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 16:06:25 UTC Slot 452,013,464, which is the chain's own clock for this moment. |
| Creation block | 12 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 211 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-09-30 16:07:01 UTC +36s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 16:17:58 UTC +11m 34s
1.950e-6 SOL per token.
Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a
decoded one.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 22 launches from 19 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 3 other creator wallets, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 4 creator wallets. See the linked wallets → |
Pool
| Liquidity | 19.0 SOL |
| Read from chain | 2026-09-30 21:00 UTC, just now |
What this launch claimed to be
| Name | super intelligence |
| Metadata held | sha256 3f82d36f1729cc1301a5965fa33bb9cfb0467510ed3b9e8d42aded3fc352042f · 294 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 2df982d729cab55dd92f3fba8e1e9bfaa9c703048ed5f9e217075fbc4c1a53e0 · 7,066 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 16:06 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.