---
title: "Rescan a transaction"
method: POST
path: "/v1/cryptos/{cryptoCode}/rescan"
tags: ["Blockchain"]
---

# Rescan a transaction

`POST /v1/cryptos/{cryptoCode}/rescan`

NBXplorer does not rescan the whole blockchain when tracking a new derivation scheme. This means that if the derivation scheme already received UTXOs in the past, NBXplorer will not be aware of it and might reuse addresses already generated in the past, and will not show past transactions.

By using this route, you can ask NBXplorer to rescan specific transactions found in the blockchain. This way, the transactions and the UTXOs present before tracking the derivation scheme will appear correctly.

## Path parameters

- `cryptoCode` string, required

## Request body

- object
  - `transactions` union[] — The transactions to rescan
    - union
      - object
        - `transactionId` string — The transaction hash to rescan.
        - `transaction` string — The transaction to rescan.
        - `blockId` string — The block hash where the transaction is located.
      - object
        - `transactionId` string — The transaction hash to rescan.
      - object
        - `blockId` string — The block hash where the transaction is located.
        - `transaction` string — The transaction to rescan.

## Response `200`

Rescan initiated successfully.

---

[API](https://skmtc.net/btcpayserver/apis/nbxplorer-api.md) · [All operations](https://skmtc.net/btcpayserver/apis/nbxplorer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/btcpayserver/nbxplorer-api/revisions/208cac39e31a/schema)