$Slop
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.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-23 16:13 UTC |
| Creator | 14nzxvi1re2WrXQf1uBbZNqGMJcTDhVDmRdKkfVF27h3 |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 25 distinct wallets, not counting the creator, bought on the bonding curve: 3 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 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 | JB354tBo93bAXaAHi18FR1… slot 449,754,210
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-23 16:13:55 UTC Slot 449,754,210, 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 | 3 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-23 16:15:22 UTC +1m 27s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-23 16:15:24 UTC +1m 29s
2.614e-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 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 2 launches from 1 creator wallet, including this one. See them → |
| This creator | 1 earlier launch, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-25 03:39 UTC, just now |
What this launch claimed to be
| Name | Infinite Slop |
| Description | THE INTERNET HAS BECOME SLOP. AI slop. Brainrot. Engagement bait. NPCs. Algorithms feeding algorithms. We didn’t create the slop. We simply accepted it. $SLOP — CONSUME THE SLOP. |
| Metadata held | sha256 c8113bbf8b26e24f1dc590cf14b29eef034a832270bd63d71f5b2fcaafc4d1e3 · 386 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-24 16:15 UTC. |
| Picture held | sha256 40f36ad2ac9710b05282aafeaea063d2e9dd719bb27f81d06654445d9cacbbd1 · 574,510 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-23 16:14 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.