Transaction Audit Log

WHAT IT DOES

Transaction Audit Log gives DeFi protocols, compliance teams, and auditors a comprehensive tool for logging and auditing blockchain transactions. It reads live on-chain data including transaction history, transaction receipts, event logs, contract state changes, timestamp data, and gas usage records. You can fetch any transaction, log audit entries with comments, generate audit reports, update audit configurations, and export audit logs. The tool shows you in real time the transaction details (from, to, value, gas used, status), audit entries count, and audit configuration state—so you can maintain comprehensive transaction audit trails for regulatory compliance.

HOW TO USE

Connect your EVM wallet (must be the contract owner or authorized address). Enter the audit log contract address, transaction hash to audit, and an optional audit comment. Use "Fetch transaction" to retrieve transaction details and receipt. Click "Log audit entry" to record an audit entry on-chain with your comment. "Generate audit report" creates a report from the contract state and transaction data. "Update audit config" changes active status and retention period. "Export audit log" downloads the audit data as JSON. Each action generates a transaction you review and sign in your wallet.

TECHNICAL APPROACH

This tool queries live on-chain data using ethers v5.7.2. It fetches transaction data using getTransaction() and transaction receipts using getTransactionReceipt() to access full transaction details including gas usage, logs, and status. It calls logAuditEntry(), getAuditEntries(), getAuditConfig(), updateAuditConfig(), and getLastAuditTimestamp() on the audit contract to manage and query audit state. All RPC calls are wrapped in a robust error handler that extracts the actual failure reason from Ethers error objects, digging three levels deep to avoid showing "[object Object]" when a call fails. Transaction costing uses receipt.effectiveGasPrice post-EIP-1559 rather than tx.gasPrice, which overstates actual spend.

WHAT IT CANNOT SEE

This tool cannot verify off-chain transaction data or guarantee that all transactions are logged correctly. It cannot see transactions that occurred before the audit contract was deployed. It cannot detect events from contracts not connected to the current network. It cannot verify the authenticity of transaction data beyond what is recorded on-chain. It cannot account for logs that were not indexed or are not accessible via the RPC provider. The tool provides transaction auditing based on available data, but it does not guarantee that the audit log is complete or that all transactions were captured.

PLEASE NOTE

This tool supports EVM‑compatible chains only (Ethereum, Goerli, Sepolia, Arbitrum, Optimism, Polygon). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. This is a read‑write tool that requires signing transactions—always verify the audit contract address, transaction hash, and comments before approving. No contract addresses are hardcoded; you paste the contracts you are managing. The tool is free and open under the BotGentz PLAYBOOK‑C specification.