> ## Documentation Index
> Fetch the complete documentation index at: https://www.bitnob.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bitnob API requests authenticate with an `X-Auth-Client` API key header against https://api.bitnob.com.
> Always use the sandbox environment for testing. Never put live API keys in sample code.
> Money amounts are integers in the smallest unit of the currency (satoshis for BTC, cents for fiat). Never use floats.
> Every state-changing request takes a client-supplied `reference` and must be treated as idempotent on retry.
> Quotes expire. Re-quote rather than reusing a stale quote id.

# Blockchain explorer guide

> How to use block explorers to confirm transfers, read confirmation depth, and diagnose stuck transactions.

How to confidently investigate, confirm, and troubleshoot stablecoin transactions across supported chains.

## Why this matters

Every stablecoin transaction, deposit or payout, touches a blockchain. Start from the [transaction record](https://www.bitnob.dev/api-reference/transactions/get-transaction-by-id.md) in the API, then confirm it on-chain. Explorers are your eyes on-chain, allowing your team to:

* Confirm if a transfer happened
* Understand why a deposit hasn’t been credited
* Catch customer mistakes early (wrong token, wrong chain, failed tx)
* Backtrace issues without waiting on engineering

With Bitnob supporting multiple chains, your Ops, Finance, and Support teams need to know how to read each explorer and interpret key transaction signals correctly.

## What is a blockchain explorer?

A blockchain explorer is a real-time search engine for blockchains. It lets you:

* Look up wallet addresses, including the deposit addresses you [issued](https://www.bitnob.dev/api-reference/addresses/generate-address.md) through Bitnob
* View stablecoin transfers (e.g. USDT, USDC)
* See whether a transaction is confirmed
* Decode failed transactions, gas used, and token details
* Spot errors like wrong chain or unsupported token usage

Think of it like your Stripe dashboard’s activity log, but public, transparent, and immutable.

## How to investigate a transaction

Let’s say a customer says:

> “I sent \$100 USDT to my deposit address, but I haven’t received anything.”

Your process:

**Step 1: Ask for the transaction hash (txHash)**

Tell them:

> “Please share the transaction hash from your wallet or exchange. It’s a long string like 0xabc... or 7f3a... depending on the chain you used.”

**Step 2: Paste it into the right explorer**

| Chain | Explorer |
| - | - |
| Ethereum | [https://etherscan.io](https://etherscan.io) |
| BSC | [https://bscscan.com](https://bscscan.com) |
| Polygon | [https://polygonscan.com](https://polygonscan.com) |
| Tron | [https://tronscan.org](https://tronscan.org) |
| Solana | [https://solscan.io](https://solscan.io) |
| Stellar | [https://stellarchain.io](https://stellarchain.io) |
| Arbitrum | [https://arbiscan.io](https://arbiscan.io) |
| Base | [https://basescan.org](https://basescan.org) |
| Optimism | [https://optimistic.etherscan.io](https://optimistic.etherscan.io) |
| Plasma | [https://plasmascan.to/](https://plasmascan.to/) |

If you don’t know which chain they used, you can guess from the txHash format:

* 0x... → Ethereum, BSC, Polygon, Arbitrum, Base, Optimism, Plasma
* 64 hex characters with no 0x → Tron or Stellar
* Base58 → Solana

## What to look for

Compare each of these against the Bitnob side of the record: the hash, amount, chain and address fields on the [webhook payload](https://www.bitnob.dev/docs/stablecoins/address-webhook-events.md#webhook), or on the [transaction record](https://www.bitnob.dev/api-reference/transactions/get-transaction-by-id.md).

| Section | What to Look for | Why It’s Important |
| - | - | - |
| Status | Success or Confirmed | Tells you the tx was accepted by the chain |
| Confirmations | Depends on the chain and deposit value: Ethereum 12 to 64, BSC 15 to 100, Tron 19 to 50, Solana 32 to 64 | Less than required = Bitnob won’t credit it |
| To Address | Must match the Bitnob deposit address | If wrong, funds are unrecoverable |
| Token Used | Must be real USDT/USDC, not a fake copy | Check contract address |
| Token Transfer | Found in a Token tab (ERC-20, BEP-20, SPL) | Stablecoin transfers live here |
| Amount | Match against what was expected (e.g., \$100) | Validate value integrity |

## Explorer examples

### Ethereum / BSC / Polygon

* Use “ERC-20 Token Txns” or “BEP-20 Token Txns” tab
* Confirm USDT contract matches official one
* USDT (BSC): `0x55d398326f99059ff775485246999027b3197955`
* Look at gas price if tx failed
* Reverts often say why: “out of gas”, “invalid opcode”

### Tron

* Use Tronscan.org
* Check “TRC-20 Transfer” tab
* Confirm the required confirmations: 19 to 50, depending on deposit value
* Address format: starts with T

Watch out for:

* Token sent using TRX instead of USDT

### Solana

* Use Solscan.io
* Paste the address or txHash
* Confirm token is USDT in the “Token Transfers” list
* Bitnob needs 32 to 64 confirmations, depending on deposit value

## Teach through examples

### Confirmed deposit (Ethereum)

* Status: Success
* To: Bitnob-issued address
* Confirmations: 30
* Token: USDT
* Contract: Matches official USDT ERC-20

→ For a deposit under \$100,000, the webhook should have been sent and the wallet credited. Larger deposits need up to 64 confirmations.

### Wrong chain

Customer was given a Tron USDT address (TRC-20), but they sent via Ethereum (ERC-20).

**How to detect:**

* Their txHash starts with 0x...
* It only shows activity on etherscan.io, nothing on Tronscan
* Bitnob didn’t detect anything → the address wasn’t valid on Ethereum

**Response:**

> "You sent USDT using Ethereum, but the address we gave you only works for USDT on Tron. These are separate networks. Unfortunately, the funds may be lost."

### Stuck pending payout

A transfer from Bitnob to an external wallet has been stuck in pending for 20+ minutes.

**Steps:**

1. Search for txHash on explorer
2. Check:
   * Is the tx still pending? → network congestion
   * Did it fail? → out of gas, contract revert
   * Was it never broadcast? → contact engineering
3. Retry or escalate via reference ID and chain

## Visual cheatsheet

| Chain | Address Format | Txhash Format | Token Tab Name |
| - | - | - | - |
| Ethereum | 0x... | 0x... | ERC-20 Token Txns |
| BSC | 0x... | 0x... | BEP-20 Token Txns |
| Polygon | 0x... | 0x... | ERC-20 Token Txns |
| Tron | T... | 64 hex characters | TRC-20 Transfers |
| Solana | base58 | base58 | Token Transfers |
| Stellar | G... | 64 hex characters | Payments |

## Bonus tips for ops dashboards

* Include "View on Explorer" button in every transaction record, built from the hash returned by [Get All Transactions](https://www.bitnob.dev/api-reference/transactions/list-transactions.md)
* Show a “Copy txHash” shortcut
* Auto-detect incorrect confirmations and flag them
* Flag tokens that don’t match official contracts
* Add internal note: Explorer confidence: ✅ Confirmed / ⚠️ Not enough confirmations / ❌ Wrong chain


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.