bch transaction derived
api.blockchain.infoMarket dataderived
POST https://api.blockchain.info/explorer-gateway-kt/x402/bch/transaction
passlisted in Coinbase#2 by calls of 55 on this host
0.001 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 3
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-01 21:40 UTC
- First observed by TOLLderived
- 2026-10-01
- Pricederived
- 0.001 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 10 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
TOLL's first observation of bch transaction was 2026-10-01.
At api.blockchain.info, bch transaction takes POST requests, is listed in the Coinbase registry, and falls under market data by TOLL's rules.
On Base, bch transaction asks 0.001 USDC per call.
Callers of bch transaction supply a json body with the field txId.
bch transaction answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-02.
bch transaction declares json output without an example.
With 55 endpoints listed on api.blockchain.info, bch transaction is tied 2nd by calls with 3 others.
It accounts for 3% of the calls counted across the host.
bch transaction drew 3 calls from 2 unique payers in the trailing 30 days.
The last call to bch transaction came 3 days before the snapshot, 2026-10-01.
Closest in price to bch transaction within market data: send token at topagentx402.vercel.app and stocks at ozmium.org.
bch transaction is among the cheapest in market data; 0% of comparable listings ask less.
The wallet paid by bch transaction is the payee of 55 endpoints on one host.
The seller's tags on bch transaction are ai-agent and Bitcoin Cash.
The price of bch transaction is declared by 629 other listings in market data too.
the payment options, as of 2026-10-04 12:19 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.001 USDC | exact | 0x995ffe…e2d8e0 |
the checks, as of 2026-10-04 09:23 UTC · method · pinnableendpoint answered HTTP 402
bazaar.info.output.example· advisory, does not affect the verdict · an output example is provided (advisory)
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 09:23 UTC | pass | 1 | daily-2026-10-04 |
| 2026-10-03 04:31 UTC | pass | 1 | daily-2026-10-03 |
| 2026-10-02 13:42 UTC | pass | 1 | daily-2026-10-02 |
| 2026-10-02 03:09 UTC | pass | 1 | new-after-daily-2026-10-01 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-01 21:40 UTC · method · live
The input and output block
{
"input": {
"body": {
"txId": "abc123..."
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"format": "application/json"
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-04 12:19 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "bch transaction on api.blockchain.info", snapshot of 2026-10-04 12:19 UTC. https://tollindex.com/e/api-blockchain-info-explorer-gateway-kt-x402-bch-transaction-28e1af/at/2026-10-04T12-19Z. Accessed [access date].
BibTeX
@misc{toll-e-api-blockchain-info-explorer-gateway-kt-x402-bch-transaction-28e1af-2026-10-04T12-19Z,
author = {TOLL},
title = {bch transaction on api.blockchain.info},
howpublished = {\url{https://tollindex.com/e/api-blockchain-info-explorer-gateway-kt-x402-bch-transaction-28e1af/at/2026-10-04T12-19Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-04 12:19 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.