Did this Base USDC Transfer log actually match?
Check an expected recipient, six-decimal USDC amount and optional logIndex against a transaction receipt obtained from the public Base RPC. Unlike comparing two self-reported CSV files, this inspects a blockchain node's current event data.
Match a particular ERC-20 event, not just an amount
Use only a public Base mainnet transaction hash that you are authorized to examine. Nothing is sent until you click Verify. Browser inputs remain in this tab; the public RPC sees the hash. No CSV or invoice/customer names are sent.
| Log index | Receiver (public) | USDC |
|---|
A match is not proof the invoice belongs to a business, was economically due or satisfies accounting obligations. The RPC can be stale, rate-limited or incorrect. The finalized-block label is the provider's report, not an independent L1 settlement audit.
What this tool does and does not verify
This checker accepts only Base chain ID 8453, a successful mined transaction receipt, the native Circle USDC token contract, a well-formed ERC-20 Transfer event, and an exact recipient/atomic amount match. It uses tx_hash:log_index to distinguish events in the same transaction. A match against an RPC-designated finalized block is labeled as such, not presented as legal or accounting proof.
It does not check who owns a wallet, map transfers automatically to real invoices, catch sanctions, validate exchange deposits, handle fiat off-ramps, value tokens for taxes, or protect against fraudulent invoices. It does not require MetaMask, authenticate an account or hold/send funds. Only one public RPC is queried; no fallback when access is restricted or unavailable.
If you want to compare your own invoice and self-reported export CSVs with zero external network calls, use the separate free offline CSV candidate matcher. Its synthetic transactions are deliberately fake; never use them here as real onchain examples.
Need batch checks mapped to your invoice CSV schema?
We can discuss a conditional 49 Base USDC fixed-scope first milestone: a deterministic local CSV-format adapter and small acceptance test harness against up to 50 invented/authorized rows, with one revision. Onchain node hosting, live treasury monitoring, custody, compliance and financial certification are not included. Price and contract are proposals only, not an order or proof of demand.
The Korea-based human owner and buyer must first agree scope, authorized synthetic data, identity and payout details, AI-assisted development, ownership, acceptance tests and refund/cancellation terms. No funds required to use the tools.
Using the free tool and found a problem? We welcome unpaid, candid feedback about which public receipt pattern fails and what a useful report should contain. You may use our existing project inquiry form for feedback or a possible pilot question. Share only a synthetic example or nonconfidential description; never provide secrets, private invoices, live employee data or wallet seed phrases. No sale or client endorsement is implied.