Ton Console
📈 Telegram kanali Ton Console analitikasi
Ton Console (@tonconsole_com) Ingliz til segmentidagi kanali faol ishtirokchi. Hozirda hamjamiyat 12 427 obunachidan iborat bo'lib, Kriptovalyutalar toifasida 8 808-o'rinni va Rossiya mintaqasida 53 195-o'rinni egallagan.
📊 Auditoriya ko‘rsatkichlari va dinamika
невідомо sanasidan buyon loyiha tez o‘sib, 12 427 obunachiga ega bo‘ldi.
12 Iyun, 2026 dagi oxirgi ma’lumotlarga ko‘ra kanal barqaror faollikka ega. Oxirgi 30 kunda obunachilar soni -141 ga, so‘nggi 24 soatda esa -3 ga o‘zgardi va umumiy qamrov yuqori darajada qolmoqda.
- Tasdiqlash holati: Tasdiqlanmagan
- Jalb etish (ER): Auditoriya o‘rtacha 9.78% darajada jalb etiladi. Nashrdan keyingi dastlabki 24 soatda kontent odatda umumiy obunachilar sonining N/A% ini tashkil etuvchi reaksiyalarni to‘playdi.
- Post qamrovi: Har bir post o‘rtacha 0 marta ko‘riladi; birinchi sutkada odatda 0 ta ko‘rish yig‘iladi.
- Reaksiyalar va o‘zaro ta’sir: Auditoriya faol: har bir postga o‘rtacha 0 ta reaksiya keladi.
📝 Tavsif va kontent siyosati
Kanal uchun tavsif kiritilmagan.
Yuqori yangilanish chastotasi (oxirgi ma’lumot 13 Iyun, 2026 da olingan) sababli kanal doimo dolzarb va katta qamrovli bo‘lib qoladi. Analitika auditoriya kontent bilan faol hamkorlik qilishini, uni Kriptovalyutalar toifasidagi muhim ta’sir nuqtasiga aylantirishini ko‘rsatadi.
tonconsole.com admin panel and analytics queries may be unavailable during this time. The functionality of the main API will not be affected.external-in) on the TON blockchain was challenging for all of us due to minor metadata differences.
Now TonAPI solves this with the normalized hash. With this method, tracking transactions is simple and reliable.
We've prepared clear examples to get you started:
- Tracking transactions from TonConnect for dApps
- Tracking manually constructed external messages
See code examples →
We’re excited to share this improvement, and soon more ecosystem tools will support it too!window.tonapi object exists in your browser.
How it works →metadata.image returns the original logo link from the Jetton metadata, while the preview field continues to provide a cached version for display.
If you haven’t yet, update your integration to use preview for displaying Jetton logos.
Everything else remains unchanged, and no action is required for existing integrations.preview has been added to the JettonInfo object. It contains a link to a cached image of the Jetton logo, specifically prepared for fast and convenient display.
2. The field metadata.image in the JettonInfo object temporarily returns the same cached image as preview. Once the migration is complete, this field will start returning the original link to the logo from the Jetton metadata.
We now recommend to display logos using the field: preview
Why are we migrating:
The goal of the migration is to resolve the mismatch between the original metadata and what our API currently provides. At present, metadata.image returns a cached image instead of the original link. After the migration, the metadata will fully reflect the original data, without any modifications.
This eliminates the need for developers to parse contract cells to retrieve original image links.
Affected Schema: JettonInfo
Affected Methods:
• getJettonInfo (/v2/jettons/{account_id})
• getJettons (/v2/jettons)
• getJettonInfosByAddresses (/v2/jettons/_bulk)
JettonInfo:
type: object
required:
- mintable
- total_supply
- metadata
- verification
- holders_count
properties:
metadata: # <- will match the original metadata after migration
$ref: '#/components/schemas/JettonMetadata'
preview: # <- new field
type: string
example: "https://cache.tonapi.io/images/jetton.jpg"
# ... other fields
Backward compatibility:
This change does not break existing integrations—your applications will continue to work without modifications. However, the image URLs for Jettons will point to the original addresses, which may affect image loading speed and the privacy of the end user.
Endi mavjud! Telegram Tadqiqoti 2025 — yilning asosiy insaytlari 
