TIGROUSDC
The curve completed in the same batch of events as the 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.
findingIt left the curve 0s after launch.
noteOnly 3.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-22 08:04 UTC |
| Creator | B41z31S72ymUKjRDFEtNGw34BxCxvq44o1miyVXGAHfM |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 15 distinct wallets, not counting the creator, bought on the bonding curve: 15 within the first 30s, 15 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 11.4 h ago and it was finished. Checked 2026-09-22 08:04 UTC. |
| Creator sold | not while we watched |
| Recorded from | 41qHGb2VTVRgt3aDmb7s6E… slot 449,319,346
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-22 08:04:24 UTC Slot 449,319,346, which is the chain's own clock for this moment. |
| Creation block | 15 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-22 08:04:24 UTC +0s Confirmed against the venue's own completion state. |
| Thirty seconds in | 15 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. |
| Highest price seen | 2026-09-22 08:11:24 UTC +6m 59s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 | No other launch we hold a picture for used this one. |
| This ticker | On 6 launches from 5 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.5 SOL |
| Read from chain | 2026-09-22 19:29 UTC, just now |
What this launch claimed to be
| Name | Leopardus Tilcayo USDC |
| Description | Leopardus Tilcayo arrived in a blue cap and chose the internet. Stable in spirit. Wild by nature. Powered by the den. |
| Metadata held | sha256 ed104ea410751fca38abad92792af310f460178e4984396d3dab22e216391083 · 465 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 d7508f8f670c637bb302fa79d384c0bbbc5851fa5a2c0ac8888439cac5a4219a · 241,424 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-22 08:04 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.