PAIRS
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 18:52 UTC |
| Creator | 9BjcGY9ZfMvS13ozDRMwCaR2toE71hiLBXXvqBcGmeiU |
| Creator took | 64.4% of supply in the first block |
| Outside buyers | 782 distinct wallets, not counting the creator, bought on the bonding curve: 441 within the first 30s, 12 bundled into the creation block. |
| Graduated | 2 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 | yes |
| Recorded from | 36eXH1H4JqfrX7cqvYYCfb… slot 452,373,380
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 18:52:02 UTC Slot 452,373,380, which is the chain's own clock for this moment. |
| Creation block | 12 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 441 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 18:54:05 UTC +2m 03s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 19:13:51 UTC +21m 49s
5.160e-7 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 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 96 launches from 88 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 13 earlier launches, 8 confirmed graduated on chain, 7 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 6 other creator wallets, across 11 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 → |
Who took the curve
One transaction bought 45 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
Pool
| Liquidity | 5.5 SOL |
| Read from chain | 2026-10-01 23:26 UTC, just now |
What this launch claimed to be
| Name | Pairlings |
| Metadata held | sha256 3923319650dfabe9ac942da96dbc6cb0cf8386c19cffcf5e449cb5fe4f9cecb3 · 336 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 60dacf04fad8cbaf66060de3eacf289d9b71b08589c64886df89b248bd37efc6 · 17,158 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 18:52 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.