DecentralChain (DCC)Install

Overview

This node interacts with the DecentralChain (DCC) blockchain to perform various operations related to accounts, tokens, transactions, utilities, and matcher services. Specifically, for the Transaction resource with the List Transactions operation, it queries the blockchain to retrieve a list of transactions associated with a specified owner address.

This operation is useful when you want to audit or monitor all transactions made by a particular address on the DecentralChain network. For example, you might use it to:

• Track incoming and outgoing payments for an account.
• Analyze transaction history for auditing or reporting.
• Integrate blockchain transaction data into other workflows or dashboards.

The node supports pagination through limit and offset parameters, allowing you to control how many transactions are returned and from which point in the transaction history.

Properties

Output

The output JSON contains the response from the DecentralChain node's /transactions/address/{ownerAddress}/limit/{limit}?after={offset} endpoint. This typically includes:

• A list/array of transaction objects related to the specified owner address.
• Each transaction object contains details such as transaction ID, type, timestamp, involved addresses, amounts, asset IDs, and other blockchain-specific metadata.
• Additionally, the output includes a debug field with metadata about the request, including:
  • The operation performed (listTransactions)
  • The API endpoint called
  • The base URL used
  • The input parameters (ownerAddress, limit, offset)
  • Timestamp of the request

No binary data is output by this operation.

Example output structure (simplified):

{
  "transactions": [
    {
      "id": "transactionId1",
      "type": 4,
      "sender": "address1",
      "recipient": "address2",
      "amount": 100000000,
      "timestamp": 1680000000000,
      ...
    },
    ...
  ],
  "debug": {
    "operation": "listTransactions",
    "endpoint": "/transactions/address/{ownerAddress}/limit/{limit}?after={offset}",
    "baseUrl": "https://nodes.decentralchain.io",
    "parameters": {
      "ownerAddress": "address1",
      "limit": 50,
      "offset": 0
    },
    "timestamp": "2024-06-01T12:00:00.000Z"
  }
}

Dependencies

• Requires access to a DecentralChain node API endpoint (default: https://nodes.decentralchain.io).
• Optionally uses credentials that may provide a custom base URL.
• Uses HTTP GET requests to query the blockchain data.
• No special environment variables are required beyond standard n8n credential configuration for API access.

Troubleshooting

• Common issues:

  • Invalid or malformed owner address: The API may return errors or empty results if the address format is incorrect.
  • Network connectivity problems: Ensure the base URL is reachable and correct.
  • Rate limiting or API restrictions on the DecentralChain node could cause failures or incomplete data.
  • Using an offset larger than the total number of transactions will result in empty results.

• Error messages:

  • Errors from the HTTP request (e.g., 404 Not Found, 400 Bad Request) usually indicate invalid parameters or unavailable endpoints.
  • If the node fails to load the underlying blockchain transaction library, it falls back to mock functions but this does not affect the List Transactions operation since it uses direct HTTP requests.
  • If the node throws an error about missing required parameters, verify that ownerAddress is provided and valid.

• Resolution tips:

  • Double-check the owner address format.
  • Verify the base URL and network connectivity.
  • Increase logging/debugging to inspect the debug output included in the node response.
  • Use smaller limits or adjust offsets to paginate through results safely.

Links and References

• DecentralChain Node API Documentation (for detailed API endpoints)
• DecentralChain GitHub Repository (for source code and libraries)
• Base58 Encoding Reference (used for attachments in other operations)

This summary focuses exclusively on the Transaction > List Transactions operation as requested.