> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# wallet/scanshieldedtrc20notesbyovk | TRON

> TRON API method that scans for shielded TRC20 notes using an outgoing viewing key (ovk). wallet/scanshieldedtrc20notesbyovk on TRON via Chainstack.

TRON API method that scans for shielded TRC20 notes using an outgoing viewing key (ovk). This method allows senders to track their outgoing shielded transactions and monitor sent payments for record-keeping purposes.

<Warning>
  The `ovk` must be provided **without the 0x prefix** and must be exactly 64 hexadecimal characters (32 bytes). The `shielded_TRC20_contract_address` must be in **hex format** (starting with 41), not base58 format. There is a block range limit: `(end_block_index - start_block_index) <= 1000`.
</Warning>

## Parameters

* `start_block_index` — the starting block number for scanning (inclusive)
* `end_block_index` — the ending block number for scanning (exclusive, max 1000 blocks from start)
* `ovk` — the outgoing viewing key for decrypting sent notes (64 hex characters, no `0x` prefix)
* `shielded_TRC20_contract_address` — the shielded TRC20 contract address to scan (hex format starting with 41, no `0x` prefix)

## Response

* `noteTxs` — array of found outgoing shielded note transactions
  * `txid` — transaction ID containing the note
  * `index` — index of the note within the transaction
  * `note` — the decrypted note details
    * `value` — note value
    * `payment_address` — recipient shielded payment address
    * `rcm` — randomness commitment
    * `memo` — optional memo field
  * `position` — position in the merkle tree
  * `is_spent` — whether the note has been spent

## Use case

The `wallet/scanshieldedtrc20notesbyovk` method is used for:

* Tracking outgoing shielded TRC20 payments for transaction history
* Monitoring sent transactions without revealing recipient details
* Building wallet interfaces that show outbound shielded transaction records
* Providing audit trails for shielded transaction activity

<Info>
  The outgoing viewing key (ovk) is derived from the spending key (sk) and is used by the sender to view shielded transactions they send. This 256-bit key allows transaction creators to track their outgoing payments without compromising the privacy of recipients.
</Info>


## OpenAPI

````yaml openapi/tron_node_api/shielded_scanshieldedtrc20notesbyovk.json post /95e61622bf6a8af293978377718e3b77/wallet/scanshieldedtrc20notesbyovk
openapi: 3.0.0
info:
  title: wallet/scanshieldedtrc20notesbyovk TRON API
  version: 1.0.0
  description: Scan for shielded TRC20 notes using outgoing viewing key
servers:
  - url: https://tron-mainnet.core.chainstack.com
security: []
paths:
  /95e61622bf6a8af293978377718e3b77/wallet/scanshieldedtrc20notesbyovk:
    post:
      tags:
        - Shielded Contract Methods
      summary: wallet/scanshieldedtrc20notesbyovk
      operationId: scanShieldedTRC20NotesByOvk
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - start_block_index
                - end_block_index
                - ovk
                - shielded_TRC20_contract_address
              properties:
                start_block_index:
                  type: integer
                  description: Starting block number for scanning
                  example: 10000000
                end_block_index:
                  type: integer
                  description: Ending block number for scanning
                  example: 10000001
                ovk:
                  type: string
                  description: >-
                    Outgoing viewing key for decrypting sent notes (64 hex
                    characters, no 0x prefix)
                  example: >-
                    0ff58efd75e083fe4fd759c8701e1c8cb6961c4297a12b2c800bdb7b2bcab889
                shielded_TRC20_contract_address:
                  type: string
                  description: >-
                    Shielded TRC20 contract address to scan (hex format, no 0x
                    prefix)
                  example: 41274fc7464fadac5c00c893c58bce6c39bf59e4c7
      responses:
        '200':
          description: Successfully scanned for outgoing shielded notes
          content:
            application/json:
              schema:
                type: object
                properties:
                  noteTxs:
                    type: array
                    description: Array of found outgoing shielded note transactions
                    items:
                      type: object
                      properties:
                        txid:
                          type: string
                          description: Transaction ID containing the note
                        index:
                          type: integer
                          description: Index of note within transaction
                        note:
                          type: object
                          description: Decrypted note details
                          properties:
                            value:
                              type: integer
                              description: Note value
                            payment_address:
                              type: string
                              description: Recipient shielded payment address
                            rcm:
                              type: string
                              description: Randomness commitment
                            memo:
                              type: string
                              description: Optional memo field
                        position:
                          type: integer
                          description: Position in the merkle tree
                        is_spent:
                          type: boolean
                          description: Whether the note has been spent

````