STEVE
The curve completed 27s 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.
noteThe creator took 26.6% of supply at launch.
findingIt left the curve 27s after launch.
noteThe creator sold while we were watching.
noteOnly 9.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 19:48 UTC |
| Creator | B9Zbs2W9VK22AHnCWiK4PqBueDFzN17RNAFu5uFozLMJ |
| Creator took | 26.6% of supply in the first block |
| Outside buyers | 38 distinct wallets, not counting the creator, bought on the bonding curve: 38 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 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 | yes |
| Recorded from | 5autNRPmH1hpKV4ZvBroy8… slot 451,740,269
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 19:48:17 UTC Slot 451,740,269, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-29 19:48:44 UTC +27s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 19:48:44 UTC +27s
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 | 38 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 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 230 launches from 166 creator wallets, including this one. See them → |
| This creator | 251 earlier launches, 2 confirmed graduated on chain, 4 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 117 other creator wallets, across 168 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 | 9.6 SOL |
| Read from chain | 2026-10-01 03:49 UTC, just now |
What this launch claimed to be
| Name | Steve coin |
| Description | Fees to @stevewilldoit via UsePaid |
| Metadata held | sha256 fd50384426a97cec6ed5ee049d2e77e1d691aa9c6ad4a48d7041f927875d8c28 · 379 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-30 19:48 UTC. |
| Picture held | sha256 09db500aa04c615765f3d018ce9a24128fbb9d3bb87719cfff9ba6e70004f71e · 111,413 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 19:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.