6 Jun 2024, 10:55 UTC77 viewsread 11 August 2026
SmartContract:#token.ethash Action: Updating circulating supply to 0.822 ETHF check here
Channel
Transaction & SC Alert
@vexascan_alert
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
47subscribers
-3 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001759162306 |
|---|---|
| Type | Channel |
| Username | @vexascan_alert |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 11 October 2026 |
| On Telegram | t.me/vexascan_alert |
Topic
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 87% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 21:56 | 47 | -1 |
| 18 Aug 2026, 23:34 | 48 | -2 |
| 12 Aug 2026, 03:05 | 50 | no change |
| 11 Aug 2026, 09:48 | 50 | first reading |
Engagement
20 posts held, back to 1 April 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 6 June 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
1 Jun 2024, 05:00 UTC86 viewsread 11 August 2026
SmartContract:#idr.speakapp Action: Updating circulating supply to 133,360,845.53 ZIDR check here
1 Jun 2024, 04:59 UTC86 viewsread 11 August 2026
SmartContract: #idr.speakapp Action: 🖨 minting new supply to 4215oskadone with total 990.00 ZIDR check here
30 May 2024, 16:36 UTC88 viewsread 11 August 2026
SmartContract:#token.ethash Action: Updating circulating supply to 0.82 ETHF check here
27 May 2024, 00:25 UTC94 viewsread 11 August 2026
SmartContract:#token.ethash Action: Updating circulating supply to 0.819 ETHF check here
24 May 2024, 01:47 UTC86 viewsread 11 August 2026
SmartContract:#token.ethash Action: Updating circulating supply to 0.818 ETHF check here
24 May 2024, 01:47 UTC74 viewsread 11 August 2026
SmartContract: #tokensawit Action: The developer has updated its smart contract code check here
24 May 2024, 01:47 UTC74 viewsread 11 August 2026
SmartContract:#idr.speakapp Action: Updating circulating supply to 133,359,855.53 ZIDR check here
24 May 2024, 01:47 UTC71 viewsread 11 August 2026
SmartContract: #idr.speakapp Action: 🖨 minting new supply to angga with total 990.00 ZIDR check here
9 Apr 2024, 01:32 UTC88 viewsread 11 August 2026
SmartContract:#token.ethash Action: Updating circulating supply to 0.782 ETHF check here
8 Apr 2024, 07:05 UTC76 viewsread 11 August 2026
SmartContract:#token.ethash Action: Updating circulating supply to 0.781 ETHF check here
7 Apr 2024, 15:31 UTC68 viewsread 11 August 2026
SmartContract:#token.ethash Action: Updating circulating supply to 0.78 ETHF check here
Showing the 12 most recent of 20 posts we hold for @vexascan_alert. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Transaction & SC Alert” (@vexascan_alert), 47 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/vexascan_alert.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.