Overview
The "Crowd BF Explorer" node allows users to explore Cardano blockchain data using 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 by its hash.
- Get Recent Orders: Detects recent decentralized exchange (DEX) orders related to a wallet by analyzing transaction metadata, focusing on platforms like Minswap and other DEXs.
This node is beneficial for blockchain developers, analysts, or enthusiasts who want to integrate Cardano blockchain data into their workflows without manually querying the blockchain. For example, it can be used to monitor wallet activity, track DEX trades, or audit transaction details programmatically.
Properties
| Name | Meaning |
|---|---|
| Network | The Cardano network to use. Options: Mainnet, Testnet. |
| Address | The Cardano address to query. Required for "Get Address Info" and "Get Recent Orders" operations. Example format: addr1qxy... |
| Limit | Maximum number of transactions to check for orders. Used only in "Get Recent Orders". Range: 1 to 100. Default is 20. |
| Operation | The operation to perform. Options: Get Address Info, Get Transaction, Get Recent Orders. |
| Transaction Hash | The transaction hash to query. Required for "Get Transaction" operation. Example: abc123def456... |
Output
The output JSON structure varies depending on the selected operation:
Get Address Info:
operation:"getAddressInfo"network: Selected networkaddress: Queried addressbalance: ADA balance in both ADA and lovelace unitsassets: List of non-ADA assets held by the addressutxos: Array of unspent transaction outputs with details (txHash,outputIndex,amount,dataHash)recentTransactions: Up to 5 most recent transactions involving the addresstotalUtxos: Number of UTXOstotalTransactions: Total number of transactions foundsuccess: Boolean indicating successnote: Optional note if address not found (likely unused)
Get Transaction:
operation:"getTransaction"network: Selected networktransactionHash: Queried transaction hashtransaction: Object containing transaction details such as hash, block info, fees, size, validity intervals, and contract validation statusinputs: Array of input UTXOs with address, amount, txHash, outputIndex, dataHash, collateral flagoutputs: Array of output UTXOs with address, amount, outputIndex, dataHashmetadata: Transaction metadata if available, otherwisenullsuccess: Boolean indicating success
Get Recent Orders:
operation:"getRecentOrders"network: Selected networkaddress: Wallet address queriedtotalOrders: Number of detected DEX orderstransactionsScanned: Number of transactions scanned to find ordersorders: Array of detected orders, each including transaction hash, timestamp, fee, size, block info, metadata, DEX detection details, order type, inputs, and outputswalletAddress: Same as queried addressqueryTime: ISO timestamp of query executionnote: Explanation that orders are detected via transaction metadata analysissuccess: Boolean indicating success
The node does not output binary data.
Dependencies
- Requires an API key credential for the Blockfrost API service.
- Uses the official Blockfrost JavaScript SDK to interact with the Cardano blockchain.
- Supports both Mainnet and Testnet endpoints of Blockfrost.
- No additional external dependencies beyond the Blockfrost API and n8n environment.
Troubleshooting
Common Issues:
- Invalid or missing API key credential will cause authentication failures.
- Querying an unused or invalid Cardano address may return empty results with a note indicating the address was not found on-chain.
- Exceeding the limit of transactions to scan (max 100) for recent orders may result in incomplete data.
- Network selection mismatch (e.g., querying a Mainnet address on Testnet) will yield no results or errors.
Error Messages:
- Errors from the Blockfrost API are caught and reported with messages like
"Cardano operation failed: <error message>". - If the node is set to continue on fail, errors are returned in the output JSON with
success: falseand error details. - HTTP 404 errors when fetching address info indicate the address likely has no on-chain activity.
- Errors from the Blockfrost API are caught and reported with messages like
Resolution Tips:
- Ensure the API key credential is valid and has access to the correct network.
- Verify the Cardano address format and network compatibility.
- Adjust the "Limit" property within allowed bounds to control transaction scanning.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- Blockfrost API Documentation
- Cardano Blockchain Explorer
- Minswap DEX
- CIP-20 Metadata Standard (relevant for detecting DEX transactions)
