🐋 链上巨鲸活动|BTC 时间:公开 Hyperliquid 成交记录中的相关强平成交出现在 2026 年 11 月 18 日 22:38 至 11 月 19 日 09:33(北京时间);Lookonchain 于 11 月 19 日发布汇总 链上记录:TechFlow 转述 Lookonchain 称,Hyperliquid 上 6 个巨鲸地址累计发生 30 次 BTC 仓位清算,涉及 618.24 BTC,按监测方估值约 3,873 万美元,报告的清算价区间为 62,055–63,364 美元。Lookonchain 列出 6 个地址。我们按这些地址查询 Hyperliquid 公开成交接口,在 11 月 18 日 22:38 至 11 月 19 日 09:33(北京时间)可见至少约 604.17 BTC 的 BTC 强平标记成交;其中两个地址的接口响应达到每次 2,000 条上限,因此无法据该次查询独立重建 618.24…

Channel
PlanX DEX-Announcement
@PlanX_info
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
52,042subscribers
-7,167 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002186392459 |
|---|---|
| Type | Channel |
| Username | @PlanX_info |
| Description | Empowering the next era of decentralized trading, where AI trades with precision, and humans own the outcome. PlanX unites AI-driven strategies, non-custodial vaults and on-chain execution—building the autonomous trading layer for the entire DeFi economy. |
| Created | 16 July 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/PlanX_info |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 15:15 | 52,042 | -341 |
| 15 Nov 2026, 14:45 | 52,383 | -388 |
| 12 Nov 2026, 03:20 | 52,771 | -648 |
| 10 Nov 2026, 03:09 | 53,419 | -141 |
| 8 Nov 2026, 15:50 | 53,560 | -101 |
| 7 Nov 2026, 12:45 | 53,661 | -73 |
| 6 Nov 2026, 11:45 | 53,734 | -140 |
| 5 Nov 2026, 13:21 | 53,874 | -60 |
| 4 Nov 2026, 15:36 | 53,934 | -101 |
| 3 Nov 2026, 16:26 | 54,035 | -93 |
| 2 Nov 2026, 17:40 | 54,128 | -92 |
| 1 Nov 2026, 14:54 | 54,220 | -70 |
| 31 Oct 2026, 17:29 | 54,290 | -65 |
| 30 Oct 2026, 18:48 | 54,355 | -90 |
| 29 Oct 2026, 19:58 | 54,445 | -106 |
| 28 Oct 2026, 19:50 | 54,551 | -71 |
| 27 Oct 2026, 16:11 | 54,622 | -99 |
| 26 Oct 2026, 14:16 | 54,721 | -63 |
| 25 Oct 2026, 17:10 | 54,784 | -71 |
| 24 Oct 2026, 14:31 | 54,855 | first reading |
Engagement
266 posts held, back to 16 July 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 210 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.056%
- avg views ÷ 52,042 subscribers
- Avg views / post
- 29.2
- 105 posts measured
- Reaction rate
- 1.54%
- reactions ÷ views · ER floor
- Posts in window
- 105
- of 266 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 105 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 19 November 2026 |
|---|---|
| Posts held | 266 (16 July 2024 – 19 November 2026) |
| Views total | 3,063 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Nov 2026, 11:44 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- 7
- Videos
- 2
- Links
- 250
Lifetime counters from Telegram’s own channel header, read 19 November 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.
- Video runtime
- 2m 02s
- Average length
- 1m 01s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
30 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 53.3% | |
| ❤🔥 | 4 | 13.3% | |
| 🔥 | 4 | 13.3% | |
| 👏 | 2 | 6.67% | |
| 😁 | 2 | 6.67% | |
| 👍 | 1 | 3.33% | |
| 👎 | 1 | 3.33% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 13 of the 266 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 266 most recent posts we hold, published 16 July 2024 to 19 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 105 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🐋 链上巨鲸活动|ETH 时间:2026 年 11 月 19 日 08:37–08:41(北京时间);链上记录时间为 00:37–00:41 UTC(11 月 18 日 19:37–19:41 EST) 链上记录:TechFlow 转述 Onchain Lens 称,地址 0x5CBC6299…5B722059(监测方标记为以太坊基金会关联地址)通过 CoWSwap 将约 1,200 ETH(约 214 万美元)转换为 USDS,并存入 Sky 储蓄合约换取 sUSDS。Blockscout 的 Ethereum 记录显示,该地址在上述时间向 CoWSwap EthFlow 提交了 1,000 ETH 与 200 ETH 两笔订单;随后一笔 Safe 执行记录显示,约 1,776,974.76 USDS 转入 Sky 储蓄合约,并铸造约 1,591,094.27 sUSDS 至该地址。200 ETH 订单交易本身未显示代币转账…
🐋 链上巨鲸活动|SOL 时间:2026 年 11 月 19 日 03:44 至 06:35(北京时间);余烬监测帖发表于 08:38(北京时间) 链上记录:余烬监测称,Pump.fun 手续费钱包向 Kraken 转出 33,390 SOL,按报告时价格估值约 243 万美元。公开 Solana 交易记录显示,地址 2p23ikTG1Da7ah7B4mtZNN2P68NfZHGPuuD6rcABCv3q 于上述时段分 6 笔转出,合计约 33,390.11 SOL,接收地址均为 6LY1JzAFVZsP2a2xKrtU6znQMQ5h4i7tocWdgrkZzkzF;Arkham 将接收地址标记为 Kraken 热钱包。发送地址的 Pump.fun 手续费钱包归因来自余烬。11 月 14 日该地址另有 64,666 SOL 转入 Kraken,已在此前独立快讯报道;本条仅记录此次新增转账。 市场背景:交易所地址流入可能增加…
🐋 链上巨鲸活动|ETH 时间:2026 年 11 月 19 日 05:49(北京时间);Onchain Lens 报告发表于 06:52(北京时间) 链上记录:Onchain Lens 监测到地址 0xEaBcf5…b9c6b1e004 收到 8,825 ETH。区块记录显示,该笔转账发生于 05:49:47,来自 Arkham 标记为 FalconX 热钱包的地址 0x1157a2…3898f4101,交易哈希为 0x0fabab…4349ce21。按监测方当时约 1,764 美元的估值,转入约值 1,557 万美元;收款地址当前余额约 9,429 ETH。链上转账及地址余额可复核,FalconX 归属依据 Arkham 地址标签,巨鲸及加权持仓成本等信息来自 Onchain Lens。 市场背景:从交易服务商地址转入个人或机构钱包可能对应资产结算或持仓调整;单笔转入不能证明市场成交或资金用途。 PlanX 判断:该地…
🐋 链上巨鲸活动|BTC 时间:链上记录为 2026 年 11 月 17 日 22:17 至 11 月 18 日 21:47(北京时间);Lookonchain 报告发表于 11 月 18 日 22:05(北京时间) 链上记录:Lookonchain 报告称,一以 bc1q7s…xyyx 标识的地址在过去 24 小时向 Binance 转入约 1,040 BTC,按其报告时估值约 6,717 万美元。逐笔核对比特币区块记录,相关窗口内该地址有 5 笔转出至同一接收地址 1KE38bzd…TAFaw,合计 1,040 BTC;该地址随后仅余约 0.02 BTC。Arkham 未将发送地址归属到具体实体。接收端的 Binance 归因来自 Lookonchain;Onchain Lens 另将其中 640 BTC 描述为与 Cumberland 相关的鲸鱼转入 Binance,但该关联未获 Arkham 地址归属确认。 市场背景…
🐋 链上巨鲸活动|BTC 时间:数据截至 11 月 17 日 UTC;TechFlow 发布时间为 11 月 18 日 15:49(北京时间) 链上记录:CryptoQuant 认证分析师 Axel Adler Jr. 报告称,截至 11 月 17 日 UTC,中心化交易所 7 日净流量为 -14,300 BTC;同期监测到的交易所 BTC 储备一周减少约 21,800 BTC 至 285 万 BTC,处于 90 日低点。分析师说明,储备下降与净流出反映同一批资金流动,应合并理解而非相加。以上为其聚合监测数据,本次未取得逐笔交易哈希及地址清单。 市场背景:该分析称 7 日净流量刚转为负值,近一年约有 18% 的观测日达到同等或更低读数;上一次相近读数出现在 10 月 7 日。数据截至 11 月 17 日 UTC,不代表所有交易所钱包或全部 BTC 的实时统计。 PlanX 判断:约 1.43 万 BTC 的一周净流出与 9…
🐋 链上巨鲸活动|XRP 时间:2026年11月17日 23:22(北京时间) 链上记录:据 XRP Ledger 交易记录,一笔 140,351,238 XRP 的 Payment 于 11 月 17 日 23:22:01(北京时间)完成,发送地址为 `rN3t4Epm69GXM1Bx42Ne1opfai7eUvmopY`,接收地址为 `rLxFWnRs97ovbPy89MrF51pkVxSoa7ezKz`,交易结果为 `tesSUCCESS`。XRPSONAR 估值约 1.359 亿美元;XRPScan API 返回的发送方和接收方名称字段为空。TechFlow 转述 CoinDesk 称,这两个接收钱包未被识别为交易所充值地址,且该来源还报告同一发送方在 11 月 6 日曾向另一个钱包转入近似数量 XRP。后续转账的哈希未在本次核验中取得。 市场背景:TechFlow/CoinDesk 将这组转账置于 XRP 下跌背景…
🐋 链上巨鲸活动|HYPE / USDC 时间:2026年11月18日 11:00(北京时间) 链上记录:据余烬监测,归属于 Abraxas Capital 的相关地址已平掉 Hyperliquid 持仓,并从质押中申请赎回约 115,370 枚 HYPE。Lookonchain 进一步报告称,该基金已清算约 2 亿美元 Hyperliquid 仓位,并将约 1.09 亿美元 USDC 转入 Binance。两篇报道均提及此事发生在 Lighter 账户 API key 泄露、约 1,039 万 USDC 损失之后;公开摘要未提供可逐笔核对的交易哈希或地址清单,归属与金额仍按监测方口径表述。 市场背景:平仓和将 USDC 转入交易所相关地址属于不同链上动作。USDC 转入 Binance 不等于卖出;HYPE 赎回申请也不代表代币已到账或已出售。 PlanX 判断:若监测方对地址归属及规模的估算准确,这代表一笔规模较大的 …
🐋 链上巨鲸活动|BTC 时间:2026年11月18日 10:05(北京时间) 链上记录:据余烬监测及其引用的 Arkham 地址记录,标记为比特币矿企 MARA 的地址在截至 11 月 18 日的近 8 天内,向外部地址转出约 1,713.9 枚 BTC,报道时估值约 1.21 亿美元。三笔转出分别约为 500 枚、847.859 枚和 366.061 枚 BTC;TechFlow 称其中约 500 枚已于 11 月 10 日报道。报道未列出地址和交易哈希,本次未能逐笔独立核对完整交易路径。 市场背景:本次报道较 11 月 10 日披露的约 500 枚转出,增加了两笔合计约 1,213.92 枚 BTC 的转出记录。目的地址及资金用途未明确;转出不等于卖出。 PlanX 判断:监测方归属的 MARA 标记地址在短期内出现累计约 1.21 亿美元外转,规模显著。由于收款地址及交易明细未完整披露,无法确认这是出售、托管迁移或…
🐋 链上巨鲸活动|ETH 时间:2026年11月18日 09:27(北京时间) 链上记录:据链上分析师余烬(EmberCN)监测,一个未公开具体地址的 ETH 地址集在约 6 天内累计买入约 95,020 枚 ETH,花费约 1.81 亿美元,均价约 1,906 美元;该地址集持有量约 649,649 枚 ETH,报道时估值约 11.8 亿美元。TechFlow 转述称,这批地址用于买入的资金已耗尽。本文未提供可逐笔复核的交易哈希或地址清单,以上数据为监测方统计,不代表已独立核验全部交易或地址归属。 市场背景:这是一组多日累计买入统计,不能据此推断地址集的后续买卖计划;报告均价也不等同于当前市场价格或已实现损益。 PlanX 判断:该监测方报告的累计买入规模显著,适合作为大额资金活动记录。地址集身份、归属关系及交易明细未在报道中披露,相关描述应视为余烬的监测归因。 来源: TechFlow:https://www.tec…
🐋 链上巨鲸活动|BTC 时间:北京时间 2026 年 11 月 17 日 19:05 链上记录:香港上市公司国际商业结算(00147.HK)在 11 月 16 日向港交所披露,于 11 月 13 日在公开市场出售 300 枚比特币,所得约 1.9225 亿港元(约 2,470 万美元)。公司预计交易录得约 1,232.5 万港元净亏损。此为公司公告披露的出售,不是单纯钱包转账;公告未提供对应链上交易哈希。 市场背景:上市公司披露的 BTC 持仓变动可作为机构资产配置的参考,但单次出售规模不能单独说明其后续配置或市场价格影响。 PlanX 判断:该公司确认减持 300 枚 BTC,金额高于机构活动门槛。公告说明交易在公开市场完成,未披露买方身份及结算链上路径。 来源: https://www1.hkexnews.hk/listedco/listconews/sehk/2026/1116/2026111601441.pd…
🐋 链上巨鲸活动|SOL 时间:北京时间 2026 年 11 月 17 日 09:30 链上记录:纳斯达克上市公司 DeFi Development Corp.(DFDV)在 11 月 16 日的公司公告及 8-K 文件中披露,11 月 9 日至 13 日期间,SOL 及等值资产持仓增加 9,482 枚,总量升至 2,619,311 枚。该公司称这是连续第 10 周增加 SOL 财库持仓。此为公司披露的财库变化,公告未逐笔列出购买交易哈希。 市场背景:公司公开财库持仓显示机构对 SOL 的持续配置,但本次单周增加规模约为百万美元级,数据按公司报告口径统计。 PlanX 判断:可确认的是 DFDV 披露的 SOL 财库净增持,不代表所有增量均由公开市场现货买入产生;公司披露包含 SOL 等值资产。 来源: https://www.sec.gov/Archives/edgar/data/1805526/0001805526…
Showing the 12 most recent of 266 posts we hold for @PlanX_info. 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
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.
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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“PlanX DEX-Announcement” (@PlanX_info), 52,042 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/PlanX_info.
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.