Skip to main content

Transactions & Provenance

This capability covers post-submission transaction tracking, event log search, and account- or contract-level history reconstruction. Use Node API to submit raw transactions and track basic status, then combine Web3 Data API and trace methods to reconstruct internal calls and movement paths. It provides an operational foundation for always-on ledger intelligence, where transactions are not only recorded but also interpreted in real time.


What You Can Build

AML and Anti-Money Laundering Workflows
Retrieve complete transaction history and Internal Transactions by account to trace fund origin and movement. By combining getTransactionsByAccount with getInternalTransactionsByAccount, you can capture both direct transfers and indirect flows routed through smart contracts.

Regulatory Audit Reporting
Extract on-chain transaction history for an audit period accurately through pagination and time filters. Use Block and Transaction domain APIs to collect the data required by regulators.

Smart Contract Event Monitoring
Use searchEvents to retrieve contract event logs by topic. This is useful for DeFi integrations, contract state change tracking, and suspicious activity detection workflows.

Token and NFT Movement History Tracking
Retrieve ERC-20 token transfer history and NFT transfer history independently for a specific account. This is useful for reconstructing asset ownership changes and analyzing movement patterns by asset type.

Post-Submission Trace Workflows
Combine eth_sendRawTransaction with eth_getTransactionReceipt, eth_getTransactionByHash, debug_traceTransaction, or trace_transaction to analyze failure causes, inspect execution paths, and support post-event auditing.

Key Capabilities

The following capabilities help you build transaction history and audit pipelines.

Key Features

Account-Based History Retrieval

Retrieve complete transaction history and Internal Transactions by account. This lets you reconstruct fund flows across both direct transfers and contract-mediated internal movement.

Event Log Search

Use searchEvents to search contract event logs by topic. Filter by event type, address, and block range to extract only the data you need.

Token and NFT Transfer Tracking

Retrieve ERC-20 and NFT transfer history independently. This is useful for reconstructing ownership changes and analyzing movement patterns for specific assets.

Block-Level Retrieval

Retrieve all transactions included in a specific block. This supports block-based audit reporting and time-specific on-chain activity reconstruction.

Node API-Based Basic Tracking

Combine eth_getTransactionByHash, eth_getTransactionReceipt, and eth_getBlockByNumber to track immediate status after submission, block inclusion, and final execution results.

Execution Path Analysis

Use debug_traceTransaction and trace_transaction methods to analyze internal calls and execution paths in depth. This is useful for root cause analysis, compliance reviews, and audit trails.

Single Source of Truth Reconstruction

Connect transactions, Internal Transactions, event logs, and asset movement data into a single reference dataset for audit and reconciliation. This reduces validation costs across fragmented ledgers and simplifies consistency checks between institutions.

How It Works

Build a transaction history pipeline through the following process:

  1. Identify the target account address, transaction hash, or block number
  2. If submission or raw tracking is required, use eth_sendRawTransaction, eth_getTransactionByHash, eth_getTransactionReceipt, and eth_getBlockByNumber to verify basic state
  3. Retrieve transaction history through Web3 Data API with time filters and pagination
  4. If needed, use getInternalTransactionsByAccount and getInternalTransactionsByTransactionHash to retrieve indirect flows routed through smart contracts
  5. Use searchEvents, debug_traceTransaction, and trace_transaction to enrich event context and execution paths
  6. Use Webhook or Stream to receive post-submission state changes asynchronously and connect them to internal analytics systems
  7. Feed normalized JSON data into audit reporting, AML systems, and risk engines

API Endpoints

The table below maps common transaction history and provenance requirements to the corresponding Nodit APIs.

RequirementAPIProductReference
Submit signed transactionseth_sendRawTransactionElastic NodeAPI Reference
Retrieve transaction status after submissioneth_getTransactionByHashElastic NodeAPI Reference
Verify final receipts after submissioneth_getTransactionReceiptElastic NodeAPI Reference
Track blocks for basic execution contexteth_getBlockByNumber / eth_getBlockByHashElastic NodeAPI Reference
Debug execution pathsdebug_traceTransactionElastic Nodedebug_traceTransaction
Trace internal executiontrace_transactionElastic Nodetrace_transaction
Retrieve transaction history by accountgetTransactionsByAccountWeb3 Data APIGet Transactions By Account
Track Internal Transactions by accountgetInternalTransactionsByAccountWeb3 Data APIGet Internal Transactions By Account
Retrieve Internal Transactions for a specific transactiongetInternalTransactionsByTransactionHashWeb3 Data APIGet Internal Transactions By Transaction Hash
Retrieve token transfer historygetTokenTransfersByAccountWeb3 Data APIGet Token Transfers by Account
Retrieve NFT transfer historygetNftTransfersByAccountWeb3 Data APIGet NFT Transfers By Account
Search event logssearchEventsWeb3 Data APISearch Events
Retrieve transactions in a blockgetTransactionsInBlockWeb3 Data APIAPI Reference
Stream status changes in real timeStreamStreamStream Event Type
Receive asynchronous status alertsWebhookWebhookWebhook
  • Elastic Node — Submit transactions and use trace/debug methods through Node API
  • Web3 Data API — Retrieve indexed transaction history and provenance data
  • Webhook — Receive asynchronous alerts for state changes and audit events
  • Stream — Stream transactions and receipt events in real time
  • API Reference — Review full API parameters and response schemas
Get Started Now

Create a free project in the Nodit Console and start using Transactions & Provenance APIs directly.