INFECT
Only 4 outside buyers bought its curveRead 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.
findingOnly 4 outside buyers bought on the bonding curve before it graduated.
noteOnly 2.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 21:48 UTC |
| Creator | EsjkxFffUVsc392VdU4NXebfQmWZ736Gyh2WDyYSyXSP |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 4 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 24 bundled into the creation block. |
| Graduated | 46 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 | 5NxfuNzLXdGx3fp9AK8B9u… slot 451,767,247
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 21:48:58 UTC Slot 451,767,247, which is the chain's own clock for this moment. |
| Creation block | 24 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 4 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 22:34:33 UTC +45m 36s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 22:34:33 UTC +45m 36s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 3 launches from 3 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.0 SOL |
| Read from chain | 2026-10-01 12:58 UTC, just now |
What this launch claimed to be
| Name | Infect |
| Metadata held | sha256 b9d93d5f404f351fba987dccef5b204ae3a9e66c28c7cb2a0141dfe16cdc86de · 295 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 21:50 UTC. |
| Picture held | sha256 b72a1aaa433cf98def1d8c31b7d925debbe7f3593961a2ee10f88aa94f87b109 · 7,320 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 21:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.