Pumpkin In
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-09-29 20:51 UTC |
| Creator | 7A9npoVDvtLdouGHKnVVZsXdEkjDv8xaTK6F3FExiWr3 |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 33 distinct wallets, not counting the creator, bought on the bonding curve: 9 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.4 days ago and it was finished. Checked 2026-09-29 21:02 UTC. |
| Creator sold | yes |
| Recorded from | 2oDnZxzf1j5ZhN5uK6MYzG… slot 451,754,316
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 20:51:09 UTC Slot 451,754,316, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 9 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-29 20:52:21 UTC +1m 13s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-29 20:55:00 UTC +3m 52s
1.998e-6 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. |
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 8 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 7 launches from 1 creator wallet, including this one. See them → |
| This creator | 39 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 06:36 UTC, just now |
What this launch claimed to be
| Name | Pumpkin Inu |
| Metadata held | sha256 58958776638981431ac2190d8e8a51fc506498381cce72a9ca82fe7289e300c0 · 303 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 20:52 UTC. |
| Picture held | sha256 97fb23e13eac404651c87a56e91c8d5285d5a078b98924ccacbeff85d4557415 · 107,205 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:51 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.