PUTIN
Checked, no markers foundWe watched this launch and checked it against every marker we record. None of them is present: the creator kept 9.8%, 734 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. A statement about what we checked, not a judgement about the token.
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.
At launch
| Created | 2026-10-01 05:44 UTC |
| Creator | 4e1XVSUGHBJQU9oaxr4SdkaRUWzncs79KmPcvoQQ4mfu |
| Creator took | 9.8% of supply in the first block |
| Outside buyers | 734 distinct wallets, not counting the creator, bought on the bonding curve: 121 within the first 30s, 5 bundled into the creation block. |
| Graduated | 6 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 | 3wr2z97HqSBzyz5LoxpCqK… slot 452,196,722
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 05:44:02 UTC Slot 452,196,722, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 121 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-01 05:50:08 UTC +6m 06s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 05:57:14 UTC +13m 12s
1.071e-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 7 launches from 6 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 122 launches from 65 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. 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 | 146.9 SOL |
| Read from chain | 2026-10-01 09:56 UTC, just now |
What this launch claimed to be
| Name | Put In |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 fc57fa2eea80e3c3a50c7803eb41d5934c70ce83b7dfe679257e9e1a4f0f4e76 · 432 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 1e095ce5a81823787678aa34f284633beef88e7e5a440f3ccae02ba800baa8a9 · 3,976 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 05:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.