Валидатор "Криптаны" отправил транзакцию включения на блоке #39073686 2026-08-07 23:22:51 UTC
Channel
Minter Validator Log
@minter_validator_log
On this record: Growth · Engagement · Posts · Citations · Cite this entry
50subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001250613001 |
|---|---|
| Type | Channel |
| Username | @minter_validator_log |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/minter_validator_log |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 15:13 | 50 | +1 |
| 21 Aug 2026, 17:17 | 49 | -1 |
| 10 Aug 2026, 11:16 | 50 | no change |
| 6 Aug 2026, 18:17 | 50 | first reading |
Engagement
20 posts held, back to 1 August 2026 — 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Валидатор "Криптаны" получил бан на блоке #39056405 до блока #39073685
Валидатор "Криптаны" отправил транзакцию выключения на блоке #39054832 2026-08-06 18:52:02 UTC
Валидатор "Криптаны" отправил транзакцию включения на блоке #39054833 2026-08-06 18:52:06 UTC
Валидатор "$99 Validator" получил бан на блоке #39052808 до блока #39070088
Валидатор "myMiNTER.net" получил бан на блоке #39052808 до блока #39070088
Валидатор "Криптаны" отправил транзакцию включения на блоке #39048868 2026-08-06 10:00:30 UTC
Валидатор "Криптаны" получил бан на блоке #39028114 до блока #39045394
Валидатор "Криптаны" отправил транзакцию включения на блоке #39021270 2026-08-04 17:33:13 UTC
Валидатор "Криптаны" отправил транзакцию выключения на блоке #39013370 2026-08-04 05:40:15 UTC
Валидатор "Криптаны" отправил транзакцию выключения на блоке #39013367 2026-08-04 05:39:58 UTC
Валидатор "Криптаны" отправил транзакцию выключения на блоке #39004958 2026-08-03 17:00:06 UTC
Showing the 12 most recent of 20 posts we hold for @minter_validator_log. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Minter Validator Log” (@minter_validator_log), 50 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/minter_validator_log.
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.