HALL
The curve completed 12s 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.
noteThe creator took 20.1% of supply at launch.
findingIt left the curve 12s after launch.
At launch
| Created | 2026-09-30 23:23 UTC |
| Creator | 7ZV54HcwtzRhZSEPskT8ox5hn9yNocK9xpe4BQXoziaP |
| Creator took | 20.1% of supply in the first block |
| Outside buyers | 134 distinct wallets, not counting the creator, bought on the bonding curve: 134 within the first 30s, 1 bundled into the creation block. |
| Graduated | 0 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 | 355ViVrJFBxG1gKouimL8i… slot 452,111,248
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 23:23:10 UTC Slot 452,111,248, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-30 23:23:22 UTC +12s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 23:23:22 UTC +12s
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. |
| Thirty seconds in | 134 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. |
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 16 launches from 14 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 81 launches from 63 creator wallets, including this one. See them → |
| This document | Byte-identical to 2 other launches' metadata document. See them → |
| This creator | 1,401 earlier launches, 34 confirmed graduated on chain, 4 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 551 other creator wallets, across 965 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
| Liquidity | 107.9 SOL |
| Read from chain | 2026-10-01 15:55 UTC, just now |
What this launch claimed to be
| Name | Bryce Hall Coin |
| Description | Fees to @brycehall via UsePaid |
| Metadata held | sha256 ba8c91bd62c50a66394cc0c6546fd9b4c5b74c398680c9550a86800c465043ce · 395 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 dadd30580d22b760c04cf6e3b640b615def0f0025dfe2099da8e635f3e6ce28b · 5,910 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 23:23 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.