Telegram RegisterThe public register of Telegram

Channel

WalletsScan (World)

@wallets_scan

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Cite this entry

920subscribers

+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-1001374910343
TypeChannel
Username@wallets_scan
Created3 September 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/wallets_scan

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 49% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@wallets_scan/14609 · this entry21 Mar 2024, 21:00 UTC@walletsscan/1662321 Mar 2024, 21:00 UTC1.00under a minute
@wallets_scan/14611 · this entry21 Mar 2024, 21:01 UTC@walletsscan/1662521 Mar 2024, 21:01 UTC1.00under a minute
@wallets_scan/14614 · this entry21 Mar 2024, 21:01 UTC@walletsscan/1662821 Mar 2024, 21:01 UTC1.00under a minute
@wallets_scan/14615 · this entry21 Mar 2024, 21:01 UTC@walletsscan/1662921 Mar 2024, 21:01 UTC1.00under a minute
@wallets_scan/14623 · this entry21 Mar 2024, 21:01 UTC@walletsscan/1663721 Mar 2024, 21:01 UTC1.00under a minute
@wallets_scan/14624 · this entry21 Mar 2024, 21:01 UTC@walletsscan/1663821 Mar 2024, 21:01 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@walletsscan20 (8/8 hand-verifiable sample passed)1.00under a minute@walletsscan (200)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 20 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 21 March 2024 to 21 March 2024. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @walletsscan. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

9206 Aug 2026, 07:23 — 920 subscribers6 Aug 2026, 14:05 — 920 subscribers6 Aug 2026, 07:236 Aug 2026, 14:05
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 919–921 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 14:05920no change
6 Aug 2026, 07:23920first reading

Engagement

20 posts held, back to 21 March 2024the 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 20 posts for this entry, the most recent from 21 March 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Links
14,400

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

21 Mar 2024, 21:01 UTC≈2,490 viewsread 6 August 2026

To: Binance-8 From: 0x9696f59e4d72e237be84ffd425dcad154bf96976 Amount: 65 398 049 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈2,450 viewsread 6 August 2026

To: Binance-8 From: 0xdfd5293d8e347dfe59e90efd55b2956a1343963d Amount: 27 958 604 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,980 viewsread 6 August 2026

From: Binance-8 To: 0x28c6c06298d514db089934071355e5743bf21d60 Amount: 591 791 472 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈2,270 viewsread 6 August 2026

To: Binance-8 From: 0x56eddb7aa87536c09ccc2793473599fd21a8b17f Amount: 87 238 153 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈2,420 viewsread 6 August 2026

To: Binance-8 From: 0x21a31ee1afc51d94c2efccaa2092ad1028285549 Amount: 94 687 947 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,580 viewsread 6 August 2026

From: Binance-8 To: 0x28c6c06298d514db089934071355e5743bf21d60 Amount: 247 546 113 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,740 viewsread 6 August 2026

To: Binance-8 From: 0x28c6c06298d514db089934071355e5743bf21d60 Amount: 191 791 472 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,320 viewsread 6 August 2026

To: Binance-8 From: 0xdfd5293d8e347dfe59e90efd55b2956a1343963d Amount: 39 349 533 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,390 viewsread 6 August 2026

To: Binance-8 From: 0x9696f59e4d72e237be84ffd425dcad154bf96976 Amount: 41 868 948 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,480 viewsread 6 August 2026

To: Binance-8 From: 0x28c6c06298d514db089934071355e5743bf21d60 Amount: 413 750 881 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,190 viewsread 6 August 2026

To: Binance-8 From: 0x21a31ee1afc51d94c2efccaa2092ad1028285549 Amount: 69 666 120 USDT View Transaction Blockchain: ERC-20 #TetherTX

21 Mar 2024, 21:01 UTC≈1,250 viewsread 6 August 2026

To: Binance-8 From: 0x56eddb7aa87536c09ccc2793473599fd21a8b17f Amount: 32 083 938 USDT View Transaction Blockchain: ERC-20 #TetherTX

Showing the 12 most recent of 20 posts we hold for @wallets_scan. 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.

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 6 August 2026 — this entry's latest reading, not the date you are reading this.

“WalletsScan (World)” (@wallets_scan), 920 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/wallets_scan.

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.