Channel
@BlocksScan
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
50subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001574777636 |
|---|---|
| Type | Channel |
| Username | @BlocksScan |
| Description | Blocksscan.io : The Search Engine for a Decentralized BlockChain Network |
| Created | Between 1 August 2021 and 27 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BlocksScan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 11:30 | 50 | no change |
| 7 Aug 2026, 04:50 | 50 | first reading |
19 posts held, back to 27 October 2021 — 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 19 posts for this entry, the most recent from 22 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
BlocksScan pinned «Our coin XDC will be reissued on March 15th. We found some problems in the structure of the old coin and therefore we are forced to do it. The old coin will no longer be serviced. If you want to exchange an old coin for a new one, you can do it immediately…»
Our coin XDC will be reissued on March 15th. We found some problems in the structure of the old coin and therefore we are forced to do it. The old coin will no longer be serviced. If you want to exchange an old coin for a new one, you can do it immediately so as not to lose your money. To do this, you need to send your old coins to the wallet that will be indicated below. You will receive a new coin within 12 hours …
We are excited to share with the community that BlocksScan has generated a new PR to add support for XinFin XDC Network on myetherwallet : https://github.com/MyEtherWallet/MyEtherWallet/pull/3719
When a smart contract imports any other contract in the current contract, there are some cases where the verification of such smart contracts does not go through as usual. In order to verify such a smart contract, the contract needs to be flattened. https://medium.com/@tivan7404/learn-how-to-flatten-a-smart-contract-and-verify-on-blocksscan-4daca3be3ac7 #XDC
Hi #XDCNetwork community, we heard you and added Pull Request to Add Support for XinFin XDC Network on TrustWallet: https://github.com/trustwallet/wallet-core/pull/2041
We are excited to inform our community that the BlocksScan request to add XinFin's $XDC on MyCrypto has been Merged! The #XDCnetwork will be included in their next release, probably some time this week! https://github.com/MyCryptoHQ/MyCrypto/pull/4250
BlocksScan is excited to share with the community on the development of adding support for XinFin XDC Network at MyCrypto: https://github.com/MyCryptoHQ/MyCrypto/pull/4250 Soon $XDC will be added to the Mycrypto open-source tool.
BlocksScan is introducing a new RPC which will help us to handle both the transaction, functions without changing any code or we can say smart contract. Setting up Metamask for #XDCNetwork using BlocksScan's #Ethereum compatible RPC 👉 https://medium.com/@tivan7404/setting-up-metamask-for-xdc-network-using-blocksscan-ethereum-compatible-rpc-f3aebf27c9cd
To add support for XinFin XDC Network on MyCrypto - an open source tool that allows you to manage your accounts privately and securely. BlocksScan has generated Request on MyCrypto #github with all the data: https://github.com/MyCryptoHQ/MyCrypto/pull/4250
The #Rosetta interface - an middleware used to integrate blockchains into Coinbase platform has been implemented for the @XinFin #XDCNetwork by @blocksscan inorder to add $XDC in the list of projects on Coinbase. Visit XDC Network's Rosetta: https://github.com/BlocksScan/rosetta-XDCNetwork
Showing the 12 most recent of 19 posts we hold for @BlocksScan. 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.
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.
@BlocksScan named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“BlocksScan” (@BlocksScan), 50 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/BlocksScan.
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.