DecentralChain (DCC) icon

DecentralChain (DCC)

Create, sign and broadcast DecentralChain transactions, plus query blockchain data

Actions25

Overview

This node interacts with the DecentralChain (DCC) blockchain to retrieve and manage account-related data, specifically focusing on asset balances for a given account address. The "Get All Asset Balances" operation fetches all token balances associated with a specified DCC account address.

Common scenarios where this node is beneficial include:

  • Monitoring all tokens held by a specific blockchain address.
  • Integrating blockchain asset data into dashboards or reporting tools.
  • Automating portfolio tracking for DCC accounts.

For example, a user can input an account address and receive a comprehensive list of all token balances owned by that address, enabling real-time asset management or auditing.

Properties

Name Meaning
Base URL The base URL of the DecentralChain node API endpoint to use if no credential is supplied. Defaults to https://nodes.decentralchain.io.

Output

The output JSON contains the full response from the DecentralChain API endpoint /assets/balance/{address}, which returns all token balances for the specified account address.

Typical structure includes:

  • A list or map of assets with their respective balances.
  • Each asset entry usually contains identifiers such as asset ID and the balance amount in smallest units.

No binary data is output by this operation.

Example output snippet (simplified):

{
  "assetBalances": [
    {
      "assetId": "someAssetId",
      "balance": 123456789
    },
    {
      "assetId": "anotherAssetId",
      "balance": 987654321
    }
  ]
}

Dependencies

  • Requires access to a DecentralChain node API endpoint, either via a provided Base URL or through configured credentials supplying the API base URL.
  • Uses HTTP requests to communicate with the blockchain node.
  • No additional external services or environment variables are required beyond network access to the specified Base URL.

Troubleshooting

  • Network Errors: If the node cannot reach the specified Base URL, ensure the URL is correct and accessible from the n8n instance.
  • Invalid Address: Providing an invalid or malformed DCC address will likely result in an error from the API. Verify the address format before running.
  • API Response Errors: If the API returns errors, check the node's debug output for details. Common issues include rate limiting or temporary node unavailability.
  • Credential Issues: If using credentials to supply the Base URL, ensure they are correctly configured and valid.

Links and References

Discussion