The first DYOR guide covered the six dimensions of evaluating a tokenized asset and the 36 questions worth asking. This one goes deeper: how to actually use blockchain tools — block explorers, RPC endpoints, and on-chain data — to verify the claims that tokenized asset issuers make. The tools are public and free. Most investors never use them. Most projects never teach their users how.

That last point deserves its own article.

Why Block Explorers Are the Most Underused RWA Tool

Every tokenized asset issued on a public blockchain leaves a permanent, publicly readable record. Every mint, transfer, redemption, and administrative action is logged on-chain. You do not need permission to read it. You do not need an account. You need a browser and the contract address.

A block explorer is the interface for reading that record. Etherscan for Ethereum and ERC-20 tokens. Solscan for Solana. XRPL Explorer for XRP Ledger. Polygonscan for Polygon. Each one lets you look up any contract address and see: how many tokens exist, who holds them, what transactions have occurred, when they occurred, and whether any administrative actions (minting, burning, freezing) have been taken.

For an RWA investor, this means you can verify: Does the token supply match what the issuer reports? Are redemptions actually being processed? Has the issuer frozen any wallets? Are there unexplained minting events? Has the contract been upgraded, and when?

None of this requires reading code. It requires reading a table.

How to Read a Token Contract on Etherscan

Go to etherscan.io. Enter the token's contract address in the search bar. You will land on the contract's main page. Here is what to look at:

Token Tracker. Shows total supply, number of holders, and the token's name and symbol. A tokenized Treasury fund that claims $2.5 billion in AUM should show a total supply whose value, at current NAV, matches approximately that figure. Significant discrepancies between what the issuer says and what the contract shows are worth investigating.

Holders tab. Shows the top wallet addresses by token balance. For institutional tokenized assets, you will often see that the majority of tokens are held by a small number of wallets. This is normal — institutional products are not widely distributed. But it also lets you see if the top holders match what you'd expect given the issuer's reported investor base. If a "globally distributed" fund has 95% of tokens in one wallet, that is worth noting.

Transactions tab. Every token transfer, mint, and burn appears here. You can see redemption patterns: are tokens being regularly burned (redeemed) in ways that match the product's stated redemption liquidity? You can see minting events: does new supply appear consistently (matching investment inflows) or in large irregular batches?

Contract tab → Read Contract. This is where smart contract functions are exposed for direct reading. Without writing any code, you can call functions like totalSupply(), balanceOf(address), or paused() to query the contract's current state. If the contract has a paused() function and it returns true, the token is currently paused — something the issuer's marketing materials may not mention.

What an RPC Endpoint Is and Why It Matters

An RPC (Remote Procedure Call) endpoint is a URL that lets you send queries directly to a blockchain node and receive raw responses. Where a block explorer is a human-readable interface built on top of blockchain data, an RPC endpoint is the data source itself.

For most investors, the block explorer is sufficient. But for anyone building an analysis workflow — comparing token metrics across multiple products, tracking supply changes over time, or monitoring specific wallets — RPC access gives you the raw data to work with programmatically.

Free public RPC endpoints exist for every major blockchain. Ethereum's public RPC is available through providers like Alchemy, Infura (free tier), and Ankr. Solana's public RPC is available through api.mainnet-beta.solana.com. XRPL's public WebSocket is at xrplcluster.com.

A simple RPC query to check an ERC-20 token's total supply:

curl -X POST [RPC_ENDPOINT] \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_call","params":[{"to":"[CONTRACT_ADDRESS]","data":"0x18160ddd"},"latest"],"id":1}'

The response is a hex value you convert to decimal. 0x18160ddd is the function selector for totalSupply() on ERC-20 contracts — the same call Etherscan makes when it shows you the total supply figure. You are reading the same data, directly.

The Bigger Question: Why Don't More Projects Teach This?

Very few blockchain projects — and almost no tokenized asset issuers — teach their users how to use block explorers or RPC endpoints to verify on-chain claims. This is a significant gap, and it is not accidental.

A project that teaches its community how to verify everything on-chain is implicitly signaling: look closely, we have nothing to hide. A project that does not teach this is not necessarily hiding anything — but it is also not encouraging verification. In a market where due diligence is difficult and many investors rely entirely on issuer-reported metrics, the absence of verification education is convenient for issuers whose on-chain data might not match their marketing.

The rare projects that do teach blockchain verification are doing something strategically important. By walking users through block explorers and explaining how to read RPC data, they build a community that understands what they are holding. That community is harder to mislead, less susceptible to FUD, and more likely to be long-term holders who understand the product — exactly the investor base a legitimate tokenized asset program wants.

For RWA specifically, on-chain verification is the entire point of the technology. The reason to put a real-world asset on a public blockchain — rather than in a conventional fund — is that the public blockchain provides an auditable, transparent record of the asset's existence, ownership, and transaction history. If investors do not know how to read that record, the transparency benefit of the blockchain is theoretical rather than actual.

A Practical Checklist

Before You Invest: Five On-Chain Checks
1. Total supply matches reported AUM. At current NAV, does the token supply × price ≈ the reported AUM? If the issuer says $500M and the contract shows $50M equivalent, investigate before proceeding.
2. No unexplained pauses or freezes. Call paused() or check for Paused events in the transaction log. If the token is paused, redemptions are blocked.
3. Minting activity is consistent with inflows. Large, irregular mint events without corresponding business announcements deserve an explanation from the issuer.
4. Redemptions are actually happening. Burn events should appear in the transaction log at a rate consistent with the issuer's stated redemption program. A fund with "daily redemptions" should show regular burn transactions.
5. Contract has not been silently upgraded. Check the contract's proxy implementation history if it is an upgradeable contract. Unannounced upgrades are a red flag.
Tools Referenced
  • Etherscan — Ethereum and ERC-20 token explorer
  • Solscan — Solana token and program explorer
  • XRPL Explorer — XRP Ledger account and transaction explorer
  • Polygonscan — Polygon / MATIC token explorer
  • Arbiscan — Arbitrum token explorer
  • RWA.xyz — Aggregated on-chain RWA market data
  • SEC EDGAR — Fund registration filings and prospectus updates

→ DYOR Part 1 — the six dimensions and 36 questions
→ DYOR Part 2 — reading EDGAR, FRED, and BrokerCheck
→ How to verify a "backed by real assets" claim yourself