Transaction Receipt API
chain.
Live transaction receipt by hash via `eth_getTransactionReceipt`: success/failed status, block number, from/to, created contract address, gas used, cumulative gas, effective gas price (wei + gwei), tx type and the emitted event logs (capped). Complements `tx` (which reads the transaction itself). Returns `found:false` for unknown/pending hashes. Reads live on-chain data with automatic endpoint fallback.
Live
Last successful check: 26 Oct 2026, 07:40 UTC.
- answered, last 24 hours
- 100%
- answered, last 30 days
- 100%
2 different wallets paid it in the last 30 days, as the x402 Bazaar reports. Payments
How addrbook checks →Connect
https:x402: an unpaid request gets a 402 with the price and pay-to wallet. addrbook never pays.
Who's behind it
- Listed by
- x402 Bazaarlast seen UTC
- Wallets named
- 0xb3f4de103f34b99f0da19b4f16d6b53a14c2194anamed by x402 Bazaar
- Listed since
Payments
- different wallets paid it, last 30 days
- 2
- paid calls, last 30 days
- 3
- last paid call (UTC)
As the x402 Bazaar reports, from payments Coinbase's facilitator settled. Read . addrbook has not counted these payments itself.
How it asks to be paid
| Network | Price | Paid in | Settled by | Pays to |
|---|---|---|---|---|
| Base | $0.003 | USDC | Per request | 0xb3f4de103f34b99f0da19b4f16d6b53a14c2194a |
From its own 402 answer at UTC. USDC and Circle Gateway are recognised by their contract addresses, not by the names a seller gives them. How payments are read
Checks by endpoint
| Host | Protocol | State | Last checked (UTC) | Last answered (UTC) | 24 hours | 30 days | Tools |
|---|---|---|---|---|---|---|---|
| chain. | x402 | Live | 100% | 100% | — |
Also listed as
Other entries that share an endpoint with this one.