DecentralChain (DCC)

Overview

This node interacts with the DecentralChain (DCC) blockchain, enabling users to create, sign, broadcast, and query various types of blockchain transactions and data. Specifically, for the Transaction resource and the Get Transaction operation, it retrieves detailed information about a specific transaction on the DCC blockchain by its transaction ID.

Common scenarios where this node is beneficial include:

• Verifying the status and details of a particular blockchain transaction.
• Auditing or tracking transactions for accounting or compliance purposes.
• Integrating blockchain transaction data into workflows for further processing or notifications.

Practical example:

• A user wants to confirm that a token transfer transaction was successfully processed on the blockchain. They provide the transaction ID, and the node fetches all relevant details such as sender, recipient, amount, fees, and confirmation status.

Properties

Output

The output JSON contains the full details of the requested transaction as returned by the DecentralChain API. This includes fields such as transaction type, ID, sender, recipient, amounts, timestamps, and other blockchain-specific metadata.

Additionally, the output includes a debug object providing:

• The operation performed (getTransaction).
• The API endpoint used.
• The base URL.
• The parameters sent (transaction ID).
• A timestamp of when the request was made.

Example output structure (simplified):

{
  "id": "transactionId",
  "type": "...",
  "sender": "...",
  "recipient": "...",
  "amount": "...",
  "timestamp": "...",
  "fee": "...",
  "proofs": [...],
  "debug": {
    "operation": "getTransaction",
    "endpoint": "/transactions/info/{transactionId}",
    "baseUrl": "https://nodes.decentralchain.io",
    "parameters": {
      "transactionId": "..."
    },
    "timestamp": "2024-06-xxTxx:xx:xx.xxxZ"
  }
}

No binary data output is produced by this operation.

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 GET requests to query the blockchain data.
• No external API keys are explicitly required for this read-only operation, but credentials can be optionally configured for other operations.

Troubleshooting

• Common issues:

  • Incorrect or missing transaction ID parameter will cause the API call to fail or return an error.
  • Network connectivity problems or incorrect Base URL will prevent successful API calls.
  • If the DecentralChain node API is down or unresponsive, the node will throw errors.

• Error messages:

  • "Library loading failed": Indicates internal library for transaction creation/signing could not be loaded; however, this does not affect the getTransaction operation which uses direct HTTP requests.
  • HTTP errors from the API (e.g., 404 Not Found) typically mean the transaction ID does not exist or is invalid.
  • Timeout or network errors suggest connectivity issues or misconfigured Base URL.

• Resolutions:

  • Verify the transaction ID is correct and exists on the blockchain.
  • Confirm the Base URL points to a valid and accessible DecentralChain node API.
  • Check network connectivity and firewall settings.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

• DecentralChain API Documentation (Base URL used in examples)
• DecentralChain GitHub Repository (for source code and libraries)
• Waves Transactions Library (related signing and transaction utilities used internally)