What this guide does

The WIN block explorer at win.elevatescan.com is a useful starting point, but it is a front-end — a website that reads the chain and displays it. This guide shows you how to query the chain yourself, directly through the WIN RPC endpoint, so you are reading the same raw data the explorer reads.

Use this when you want to confirm a block number, check a wallet balance, or verify a transaction without depending on any website's rendering of that data.

What you need

  • The WIN RPC endpoint: https://rpc.win.blockfabric.net
  • Chain ID: 946
  • A terminal with curl (installed by default on macOS and most Linux systems) — or Postman, Insomnia, or any HTTP client

Full setup details including how to add the network to MetaMask are at the official Block Explorer support article.

The three calls

1. Get the current block number

This tells you how many blocks have been produced. Compare it against what win.elevatescan.com shows — they should match within a few blocks.

curl -X POST https://rpc.win.blockfabric.net   -H "Content-Type: application/json"   -d '{{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}}'

The response will include a result field in hexadecimal. Convert it to decimal to get the block number. For example, 0x20f3a1 → decimal 2,160,545.

2. Get a wallet balance

Replace 0xYOUR_ADDRESS with any wallet address you want to check.

curl -X POST https://rpc.win.blockfabric.net   -H "Content-Type: application/json"   -d '{{"jsonrpc":"2.0","method":"eth_getBalance","params":["0xYOUR_ADDRESS","latest"],"id":1}}'

The result is in wei (the smallest unit). Divide by 10^18 to get the token amount.

3. Get a transaction by hash

Replace 0xTX_HASH with any transaction hash from the block explorer.

curl -X POST https://rpc.win.blockfabric.net   -H "Content-Type: application/json"   -d '{{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["0xTX_HASH"],"id":1}}'

The response includes the block number, sender, recipient, and value of the transaction.

Read the results — hex to decimal

WIN RPC responses use hexadecimal numbers prefixed with 0x. To convert:

  • In a browser console: type parseInt("0x20f3a1", 16) and press Enter
  • In a terminal: echo $((16#20f3a1))
  • Or use any online hex-to-decimal converter

What this proves — and what it does not

A successful RPC response confirms that a live node is accepting connections at the listed endpoint and returning chain data. It confirms the chain is active. It does not confirm anything about the value of WIN tokens, the returns any participant will receive, or the future direction of the network.

Next: verify a timeline claim →

Back to: Advanced DYOR hub · Main verification guide