KRAMMED
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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.
noteOnly 8.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 01:17 UTC |
| Creator | 5cX4NGekJHvAJBcU3sxQXNtUcLbbY4C4FKvxsPNGC45w |
| Creator took | 2.0% of supply in the first block |
| Outside buyers | 240 distinct wallets, not counting the creator, bought on the bonding curve: 137 within the first 30s, 7 bundled into the creation block. |
| Graduated | 2 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 | 2p6UrDg2vMijjbg3Wb4sjk… slot 452,459,743
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 01:17:56 UTC Slot 452,459,743, which is the chain's own clock for this moment. |
| Creation block | 7 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 137 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-02 01:19:49 UTC +1m 53s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 01:19:49 UTC +1m 53s
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. |
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 2 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 2 launches from 2 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 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 | 8.8 SOL |
| Read from chain | 2026-10-02 07:00 UTC, just now |
What this launch claimed to be
| Name | Krammed |
| Metadata held | sha256 662d59bedb0ef88a6508c4593029a550608c73327a8fb89ed07b3e53da307119 · 285 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 f3e441c20263478c07459cb05bc06de6a001092ed43f5dae4b7a205ce48c5247 · 28,739 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 01:17 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.