How to Check a TON Transaction Using Tonkeeper

Accessing Transaction History in Tonkeeper

1. Open the Tonkeeper mobile application on your iOS or Android device.

2. Ensure you are logged into the correct wallet profile associated with the address you wish to audit.

3. Tap the History tab located at the bottom navigation bar.

4. Scroll through the chronological list of transactions, which displays timestamps, counterparties, amounts, and status indicators.

5. Each entry includes a unique transaction ID—tapping it reveals full on-chain metadata including block height and processing time.

Searching for Specific Transactions

1. From the History screen, locate and tap the magnifying glass icon in the top-right corner.

2. Enter either a full transaction hash, a wallet address, or a TON domain (e.g., alice.ton) into the search field.

3. Tonkeeper instantly filters results across both incoming and outgoing activity tied to that identifier.

4. Matching entries highlight contextual details such as asset type, fee deduction, and confirmation count.

5. If no results appear, verify that the hash corresponds to the TON mainnet—not testnet—and that the transaction has been confirmed.

Verifying Transaction Status and Confirmations

1. Select any transaction from the history list to open its detailed view.

2. Observe the status badge: Confirmed indicates finality; Pending means it is queued but not yet included in a block.

3. Check the “Confirmations” counter beneath the status label—TON requires only 1–2 confirmations for practical finality due to its high-speed consensus.

4. Cross-reference the displayed block number with a public block explorer like tonviewer.com or tonscan.org by pasting the same transaction ID.

5. Compare timestamps between Tonkeeper and the external explorer to detect potential UI rendering delays or sync inconsistencies.

Understanding Transaction Metadata

1. Inside a transaction detail page, identify the “From” and “To” fields—these show raw addresses unless resolved via TON DNS.

2. The “Amount” line item specifies the transferred quantity in TON or jettons, while “Fee” shows the exact gas cost deducted from the sender’s balance.

3. Look for the “Initiator” field to determine whether the action was user-triggered or bot-initiated, especially relevant for Telegram-integrated dApps.

4. Scroll down to view “Message” content—if present—which may contain encoded instructions, memo text, or smart contract call parameters.

5. A “View on Explorer” button launches an external browser window directly to the corresponding entry on tonviewer.com.

Troubleshooting Common Visibility Issues

1. If a known transaction does not appear, force-refresh the wallet by pulling down on the History screen.

2. Confirm network synchronization: navigate to Settings → Network Status and verify “Synced” appears next to “Mainnet”.

3. Disable and re-enable wallet connectivity under Settings → Wallets → [Your Wallet] → Toggle “Enable” off then on.

4. Clear local cache without deleting keys: Settings → Advanced → Clear Cache, then restart the app.

5. For cross-chain transfers involving bridges, check the destination chain’s explorer separately—Tonkeeper only tracks native TON-layer activity.

Frequently Asked Questions

Q: Can Tonkeeper display transactions from other blockchains after bridging?A: No. Tonkeeper exclusively monitors activity occurring natively on The Open Network. Bridged assets appear only once they land on TON as jettons or wrapped tokens.

Q: Why does a transaction show “Pending” for more than 30 seconds?A: This typically signals insufficient gas, network congestion during peak load, or an invalid recipient address format. Verify the destination supports TON addresses and retry with increased fee priority if available.

Q: Is it possible to recover a transaction ID if I closed the detail view?A: Yes. All transaction IDs remain accessible in the full history list. Long-press any entry to copy its hash to clipboard immediately.

Q: Does Tonkeeper store private transaction data locally?A: No. Transaction records are derived solely from public blockchain state. No personal identifiers, message contents, or metadata are stored beyond what is broadcast on-chain.