How to read a transaction on NearBlocks, step by step
Last updated: 12 November 2026 · On-chain facts checked 31 October 2026
In short: NearBlocks is a public website that shows every transaction on NEAR. You can read one in a few minutes if you go top to bottom: first the status, then who sent it and who got it, then what it did, then the steps it split into, and last the gas fee. This page does that with a real FLTC swap, so you can open it next to the page and follow along.
The transaction we will read
On 14 October 2026 at 6:09 PM ET, someone swapped FLTC for NEAR in FLTC's pool on Rhea. This is the last swap in that pool that the check page lists. Open it on NearBlocks. The ID, called the transaction hash, is HumMzbDtETZWFxv1ofeiVMcx4kb3mDANzZDEYhfeh4zy.
To read your own, paste its hash into the search box at the top of nearblocks.io. Your wallet's activity list shows the hash. I read this one on NearBlocks and again straight from a NEAR archival node on 31 October 2026, and the numbers matched. NearBlocks changes its layout from time to time, so a label may look a little different when you visit.
Step 1: the top of the page
| NearBlocks label | What it means | This example |
|---|---|---|
| Status | Whether it worked | Success |
| Block Height | Which block holds it | 219,990,030 |
| Timestamp | When it happened (UTC) | Oct 14, 2026 22:09:19 UTC, which is 6:09 PM ET |
| Shard Number | Which lane of the network ran the first step | 9 |
"Success" is the first thing to check. If it says "Failure," the failed transaction lesson explains how to read the error.
Step 2: From and To
The signer ("From") is the account that signed the transaction with its key. The receiver ("To") is the account the first action was sent to.
- From:
fb8803d7d93cac1ffc3828845c0e1c9ca194b219118b7ac36d9ffe4fd1d805e2. This is a 64-character implicit account, a key written in hex. See account names. - To:
fltc-af549c.launchpad.justhoot.near. This is the FLTC token contract.
The swap happened in Rhea's pool, but "To" is not the pool. It shows the FLTC contract because the person told the FLTC contract to pass tokens on to the pool. The pool appears later, in the steps.
Step 3: what was asked for
Near the top, NearBlocks writes a sentence: Call ft_transfer_call by (the signer) on (the FLTC contract). That is the action. ft_transfer_call is the standard call a token uses to send tokens to a contract and run something with them (see what a token contract is). Its inputs, which NearBlocks shows as arguments, were:
receiver_id:dclv2.ref-labs.near, Rhea's pool contract.amount: 10,248,247.351 FLTC (written on chain as10248247351018776121473204, because FLTC has 18 decimal places).msg: instructions for the pool. In plain words: swap through the FLTC and wNEAR pool, give mewrap.nearout, and give me at least 10.553441 of it or cancel. That minimum is the "slippage" guard from the failed transaction lesson. See what wNEAR is.
Deposit Value shows 0. The call actually attached 1 yoctoNEAR, the smallest unit of NEAR, which token contracts require as proof that a wallet approved the call. NearBlocks rounds it down to 0.
Step 4: Token Transfers
NearBlocks adds up what moved. For this transaction it lists three lines:
- 10,237,999.104 FLTC from the signer to
dclv2.ref-labs.near, the pool. - 10,248.247 FLTC from the signer to the FLTC contract itself.
- 10.768817 wNEAR burned from the pool.
The two FLTC lines add up to the full amount in the call. The second one is exactly 0.1% of it, and the FLTC contract's own log labels it transfer_fee_held. That is the FLTC token fee (see how the fee is split). Whether a plain wallet-to-wallet send is charged the same way is still unconfirmed, as the facts page says. The wNEAR line is the pool paying out: the pool unwrapped its wNEAR, and the signer received 10.768817 NEAR.
Step 5: the steps, called receipts
One transaction on NEAR is turned into receipts. Each receipt is one small job, sent to one account, and a job can create more jobs. This one made 14 receipts. The NearBlocks tabs for these (the exact tab names can change) show the order and which account ran each one. Here are the main ones, in order:
| Who ran it | What it did |
|---|---|
| FLTC contract | ft_transfer_call: moved the FLTC and called the pool |
dclv2.ref-labs.near (Rhea pool) | ft_on_transfer: did the swap and asked wrap.near to unwrap |
wrap.near | near_withdraw: turned wNEAR back into NEAR and sent it to the pool |
| Rhea pool | callback_post_withdraw_near: sent 10.768817 NEAR to the signer |
| FLTC contract | ft_resolve_transfer: checked how the pool handled the tokens |
| The network ("system") | Seven refund receipts that return unspent gas to the signer |
A "callback" is a step that waits for an earlier step to finish, then acts on its result. If any step fails, the status at the top shows it.
To watch these receipts hop from account to account one at a time, try the swap walk-through.
Step 6: gas and the fee
| NearBlocks label | This example |
|---|---|
| Transaction Fee | 0.003283 NEAR |
| Gas Limit & Usage | 180 Tgas limit | 85.505 Tgas usage |
| Burnt Gas & Tokens | 0.322 Tgas | 0.000032 NEAR |
The limit is the gas the signer set aside. The fee is what was really paid, and it is the number to trust. 0.003283 NEAR is about 32.83 Tgas at the minimum price of 0.0001 NEAR per Tgas (see gas fees).
The "usage" of 85.505 Tgas is bigger than 32.83 because NearBlocks also counts the gas shown on the seven refund receipts. Each shows 7.52 Tgas and carries no charge. That is why "usage" and "fee" do not line up neatly. The "Burnt Gas & Tokens" line is only the very first step, where the transaction became a receipt. It is a small part of the total.
Step 7: logs
Contracts can write short notes called logs. They are useful because they say what the contract thought it did. NearBlocks shows them with the receipt that wrote them. In this transaction I found four, read from the chain:
- The FLTC contract logged a standard
ft_transferevent listing the two FLTC moves from Step 4. The second move carries the notetransfer_fee_held. - The Rhea pool logged a swap event: 10,237,999.104 FLTC in and 10.768817 wNEAR out, in pool
fltc-af549c.launchpad.justhoot.near|wrap.near|10000. The 10000 at the end is the pool's fee setting, which means 1% (see liquidity pools). wrap.nearloggedWithdraw 10768817406995362128485269 NEAR from dclv2.ref-labs.near.- The FLTC contract logged
transfer_fee_settled, a record that the 0.1% fee was handled.
A log is the contract's own words. It helps you read what happened, but the balance changes in Step 4 are the ground truth.
A short checklist
- Status says Success?
- Do From and To match the accounts you expected? Check them letter by letter.
- Does the action name make sense for what you did?
- Do the token moves match what you meant to send and receive?
- Is the fee small and in line with the gas fees page?
If one answer is no, stop and read the receipts before you try again. Never share your recovery phrase with anyone who offers to help you read a transaction. See seed-phrase scams.
Words you don't know are in the glossary.
Sources
- The transaction: nearblocks.io/txns/HumMzbDtETZWFxv1ofeiVMcx4kb3mDANzZDEYhfeh4zy, also read through NEAR's archival RPC (
EXPERIMENTAL_tx_status) on 31 October 2026 - NEAR Docs, "Anatomy of a Transaction": docs.near.org/protocol/transactions/transaction-anatomy
- NEAR Docs, "Lifecycle of a Transaction": docs.near.org/protocol/transactions/transaction-execution
- NEAR Docs, "Gas (Execution Fees)": docs.near.org/protocol/transactions/gas
- NEP-141 Fungible Token standard: nomicon.io/Standards/Tokens/FungibleToken/Core