Tx-Trace

The Tx-Trace service allows traders to get an insight on transactions propagation by the BDN. With the Tx-Trace utility you can know if a transaction was private or public, what region received it first, and the timestamp each region saw it. Traders can optimize their trading bot and infrastructure to minimize latency and processing time.

The Tx-Trace utility has a built-in rate limiting defined by the account tier.

For each region, Tx-Trace will return the timestamp the transaction was processed and the time difference from the first region to process it.

REQUEST

curl

curl \
    -X GET \
    -H "Content-Type: application/json" \
    -H "Authorization: <YOUR-AUTHORIZATION-HEADER>" \
    https://tools.bloxroute.com/txtrace/<TX_HASH>

browser

https://tools.bloxroute.com/txtrace/<TX_HASH>?auth_header=<AUTH_HEADER>

parameters

Name	Description	Default
auth_header	Allows the user to include the authentication in the URL string directly. If the authentication is provided in both the header and the URL parameter, the one in the header will be used.	None
readable	Shows the time the transaction was received by each region in a neat string format.	false

RESPONSE

Examples

{"txTrace":[
    {"region":"EU United Kingdom","txTime":"2021-11-09 14:55:54.755","diff":"+0ms"},
    {"region":"EU Germany","txTime":"2021-11-09 14:55:54.762","diff":"+7ms"}, 
..  ...
    ],
"txHash":"4a0c243bc1556c665dc5de722fb425a61e446a122f60a5addefaf7c5b13c2dea",
"numberOfRegions":10}

Tx-Trace data is available only for a few hours. In case the data has been purged, the following will be displayed (this message will also be displayed for private transactions):

{"message":"received no info about transaction <TX hash> from relays"}

Rate Limiting

Tx-Trace is limiting requests if they exceed 2 requests per second. In addition, each tier has a limit to how many requests per day are allowed.

Below are the tiers limits:

Account Tier	Requests Per Day
Ultra	500
Enterprise-Elite	500
Enterprise	100
Professional	20
Introductory	2