Crowd BF Explorer icon

Crowd BF Explorer

Explore Cardano blockchain data via Blockfrost API

Actions3

Overview

The Crowd BF Explorer node allows users to explore Cardano blockchain data by interacting with the Blockfrost API. It supports three main operations:

  • Get Address Info: Retrieves balance, assets, UTXOs, and recent transactions for a given Cardano address.
  • Get Transaction: Fetches detailed information about a specific transaction using its hash.
  • Get Recent Orders: Extracts recent decentralized exchange (DEX) orders related to a wallet by analyzing transaction metadata.

This node is useful for blockchain developers, analysts, or enthusiasts who want to programmatically query Cardano blockchain data within n8n workflows. For example, you can monitor wallet activity, verify transaction details, or track DEX orders on Cardano networks.

Properties

Name Meaning
Network The Cardano network to use. Options: Mainnet, Testnet.
Transaction Hash The hash of the transaction to query. Required when operation is "Get Transaction".

Note: The provided properties are filtered for the Default resource and Get Transaction operation.

Output

The output JSON structure for the Get Transaction operation includes:

  • operation: The string "getTransaction".
  • network: The selected Cardano network (mainnet or testnet).
  • transactionHash: The queried transaction hash.
  • transaction: An object containing:
    • hash: Transaction hash.
    • block: Block hash containing the transaction.
    • blockHeight: Height of the block.
    • blockTime: Timestamp of the block.
    • slot: Slot number.
    • index: Transaction index in the block.
    • fees: Object with ADA fees in both ADA and lovelace units.
    • size: Size of the transaction.
    • invalidBefore: Slot before which the transaction is invalid.
    • invalidHereafter: Slot after which the transaction is invalid.
    • validContract: Boolean indicating if the contract is valid.
  • inputs: Array of input objects, each with:
    • address: Input address.
    • amount: Amounts involved.
    • txHash: Previous transaction hash.
    • outputIndex: Output index.
    • dataHash: Optional data hash.
    • collateral: Boolean indicating collateral input.
  • outputs: Array of output objects, each with:
    • address: Output address.
    • amount: Amounts involved.
    • outputIndex: Output index.
    • dataHash: Optional data hash.
  • metadata: Transaction metadata if available, otherwise null.
  • success: Boolean indicating successful retrieval.

The node does not output binary data.

Dependencies

  • Requires an API key credential for the Blockfrost API service.
  • Uses the official @blockfrost/blockfrost-js library to interact with the Cardano blockchain.
  • Supports both Mainnet and Testnet endpoints of Blockfrost.
  • No additional environment variables are required beyond the API key credential.

Troubleshooting

  • Common Issues:

    • Invalid or missing transaction hash will cause errors.
    • Network selection mismatch (e.g., querying a Mainnet transaction on Testnet) may result in "not found" errors.
    • API rate limits from Blockfrost could cause request failures.
    • If the transaction metadata is unavailable, the metadata field will be null but the rest of the data should still be returned.

  • Error Messages:

    • Errors from the Blockfrost API are caught and reported with their message and HTTP status code.
    • If the node is set to continue on fail, it outputs an error object with success: false and error details.
    • Otherwise, it throws a node operation error with a descriptive message like:
      Cardano operation failed: <error message>

  • Resolution Tips:

    • Verify the transaction hash format and correctness.
    • Ensure the correct network is selected.
    • Check your Blockfrost API key validity and usage limits.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion