Channel
@OxBlockify
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
16subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001985398381 |
|---|---|
| Type | Channel |
| Username | @OxBlockify |
| Description | Securing your Crypto experience one Blockchain at a time. |
| Created | 31 May 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/OxBlockify |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 21:17 | 16 | no change |
| 7 Aug 2026, 09:47 | 16 | first reading |
9 posts held, back to 31 May 2023 — 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 pageof 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 9 posts for this entry, the most recent from 4 June 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Just burned another 3,000,000 $BLOCK right now making it total of 20,000,000 $BLOCK tokens burnt and removed from the circulating supply. I keep buying back and burning every supply. 0xBlockify's $BLOCK is highly deflationary. https://bscscan.com/tx/0xc029bb5136034988264a0427e5fca6751b9e20060e40a72e5301434cc228725a Website: https://www.0xblockify.com Telegram: https://t.me/OxBlockify
🔶 0xBlockify Entered BSC TRENDING! Token: 0x0bf24718b430958de3de5aa62f2f049861b0b81c Group: 0xBlockify | Blockchain Solutions 🥇 Chart ✨ Trade ✅ Events 🔸 Trending
CMC Listing Applied with ALL necessary information valid and authorized. This will not take a while. GET READY! Ⓜ️ Ticket No: 360000493112
Check out our latest Medium post as we reveal our very first utility, 0xBlockify DEX. It's not just a DEX, it aims to be BSC’s first BlockDEX, offering a unique & innovative way for users to trade safely using private nodes and Blockify technology. Read more here: https://medium.com/@0xBlockify/0xblockify-dex-29963af2878b
Direct Link: https://t.me/+aRCRIHSs4jE2NDZl
Currently 11,000,000 (1.1%) $BLOCK tokens were sent to dead address a.k.a burnt! 🔥 https://bscscan.com/token/0x0bf24718b430958de3de5aa62f2f049861b0b81c#balances
1 MONTH LP LOCK (INITIAL) 🔼 https://mudra.website/?certificate=yes&type=0&lp=0x9f742674b07911bf5bafa8f78b68329c9a7e0390 OWNERSHIP RENOUNCED 🔼 https://bscscan.com/tx/0xa2c99504669f1e42d3314dacc3e15062dcddd3959475579a9a6b417c27f5b86b
0xBlockify | Blockchain Solutions | Renounced is being protected by @SafeguardRobot Click below to verify you're human
Channel created
Showing the 9 most recent of 9 posts we hold for @OxBlockify. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“0xBlockify | Blockchain Solutions | Renounced” (@OxBlockify), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/OxBlockify.
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.