692,588 launches on record
Coverage from 2 Sep 2026
Archive read 00:57 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

INTESTINE

The curve completed 13s after launchRead 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.

tHj6HpzsZzvfWHNCpun2NCZimEh3R8zdBmMSY7iZ6py Solscan
not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
findingIt left the curve 13s after launch.

At launch

Created2026-09-22 21:43 UTC
Creator7naFFwuEJWeWwWYQUkgAWHsxYKg3KctEuUj42JdAMidP
Creator took12.4% of supply in the first block
Outside buyersunknown distinct wallets, not counting the creator, bought on the bonding curve.
Graduated0 min after launch
Curve, read on chainNot 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 soldnot recorded - this venue's trades do not name the wallet
Recorded from6EEgDJkTLyQ8cTmhEY4z5y… slot 449,503,229
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

Order of events

Created2026-09-22 21:43:33 UTC
Slot 449,503,229, which is the chain's own clock for this moment.
Highest price seen2026-09-22 21:43:33 UTC
0.000e+0 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.
Curve completed2026-09-22 21:43:46 UTC +13s
Confirmed against the venue's own completion state.

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 pictureNo other launch we hold a picture for used this one.
This tickerOn 7 launches from 7 creator wallets, including this one. See them →
This documentByte-identical to 1 other launch's metadata document. See them →
This creator683 earlier launches, 18 confirmed graduated on chain, 4 with findings on record. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 346 other creator wallets, across 577 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

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NameIntestine Coin
Metadata heldsha256 1c3069591e1a0b1f5652675d5a18e3d87fcb37ef36748a7299933496378191e3 · 401 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-readByte-identical to the launch-time capture when re-read 2026-09-23 21:45 UTC.
Picture heldsha256 c7b8594a433c5aab51c8002e9c40d52f06047369d45dbd0b02b2717d87ad2995 · 42,887 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-09-22 21:43 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another