TUBED
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.
noteThe creator sold while we were watching.
noteOnly 3.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-28 15:48 UTC |
| Creator | 95Y9a31Vi94q38zcad3L4Fpo4xdsCdzqskpPFnGpt8WC |
| Creator took | 3.5% of supply in the first block |
| Outside buyers | 422 distinct wallets, not counting the creator, bought on the bonding curve: 89 within the first 30s, 13 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.1 days ago and it was finished. Checked 2026-09-28 16:02 UTC. |
| Creator sold | yes |
| Recorded from | dKK9sspWEtUyVGwVQQDjRx… slot 451,363,863
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-28 15:48:43 UTC Slot 451,363,863, which is the chain's own clock for this moment. |
| Creation block | 13 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 89 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-28 15:53:26 UTC +4m 43s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-28 15:53:26 UTC +4m 43s
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 23 launches from 23 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 24 launches from 24 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.8 SOL |
| Read from chain | 2026-09-29 19:02 UTC, just now |
What this launch claimed to be
| Name | TUBED |
| Description | $TUBED turns YouTube channels into community token markets, routing eligible trading fees back to verified creators 📺 Launch around any channel, track rewards openly, and let creators claim fee balances plus disclosed token allocations after verification 💰🔗 |
| Metadata held | sha256 198382bb8bf49d61603b954f9931b5452bcfdc209f2119a3e3840489d44f4081 · 648 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-29 15:50 UTC. |
| Picture held | sha256 667edb6dd5a30f1d41f5680b52a5d0d45fc2f65d91e3c2aaea3f096228b107db · 18,496 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-28 15:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.