Question 1

What does the NEAR Intents explorer show, and how do you query intent data programmatically?

Accepted Answer

The NEAR Intents explorer is a read-only dashboard for intent-based cross-chain activity. It shows aggregate volume, recent swaps, referral and affiliate leaderboards, and a searchable feed of individual intents with sender, recipient, asset, status, and timestamp. It is useful for verifying that a cross-chain swap settled, auditing solver behaviour, or building a monitoring view over intent flow.

If you need the same data inside your own tooling, the explorer is not the integration surface. You query intent history through the explorer's read-only API, and you query the underlying NEAR chain state through a NEAR RPC endpoint. Those are different jobs: the explorer API answers "what happened to this intent," while RPC answers "what is the current on-chain state of this account, block, or transaction."

This page separates the two so you can pick the right data source, avoid building against a UI that was never meant to be a backend, and keep your own indexer or dashboard reliable. For teams running production NEAR workloads, OnFinality provides NEAR RPC API access and dedicated node infrastructure alongside many other supported networks.

Question 2

NEAR Check: How to Verify Transactions, Balances, and RPC Health

Accepted Answer

A "NEAR check" usually means one of three things: confirming a transaction or account on the NEAR blockchain, verifying that your RPC endpoint is responding correctly, or validating a wallet or contract interaction before you ship. The fastest path is to use a block explorer for human-readable lookups and a JSON-RPC call for programmatic checks.

This page gives you the practical checks developers run most often on NEAR: reading an account balance, fetching a transaction outcome, confirming block height, and probing an RPC endpoint for health. It also explains when a public endpoint is enough and when you should move to a dedicated RPC provider such as OnFinality for consistent access.

NEAR uses a JSON-RPC interface with methods like `query`, `block`, and `tx`. The examples below show how to run those checks with curl and with JavaScript, and how to interpret the responses so you can tell the difference between a network issue, an RPC issue, and an application bug.

API Service

Dedicated Nodes

Enterprise Nodes

Indexer Services

Network Prototyping Tools

Staking & Validators

AI Agent

RPC documentation entries

What does the NEAR Intents explorer show, and how do you query intent data programmatically?

NEAR Check: How to Verify Transactions, Balances, and RPC Health

Never Worry about Infrastructure Again

Supported Networks

Product

Company

Resources

Near RPC Assistant

RPC documentation entries

What does the NEAR Intents explorer show, and how do you query intent data programmatically?

NEAR Check: How to Verify Transactions, Balances, and RPC Health

Never Worry about Infrastructure Again

Supported Networks

Product

Company

Resources