Aller au contenu principal

Trace Errors & Timeouts

This page covers the most common issues when running traces in Wallet Tracer and what to do about each one.

Trace Shows "Failed"​

Possible causes:

  • The entered address is not a valid Ethereum address. Check that it starts with 0x and is 42 characters long.
  • The address has no on-chain transaction history.
  • A temporary issue occurred during processing.

What to do:

  1. Verify the address format in the search bar.
  2. Check that the address has on-chain activity by opening it on a block explorer.
  3. Return to the Wallet Tracer home page and run the trace again.

If the same address consistently returns a failed trace and the address appears valid and active on-chain, contact support.

Trace Stuck on "Running"​

Traces can take several minutes to complete, particularly for addresses with extensive transaction histories or high hop counts.

What to do:

  1. Wait — a running trace is actively processing. There is no need to refresh immediately.
  2. If the trace has been running for more than 10 minutes, refresh the page.
  3. Check Trace History — the trace may have completed in the background and the result is available there.
  4. If the trace is not in History and the status still shows "Running" after a refresh, re-run the trace from the home page.

Empty or Near-Empty Graph​

A completed trace that returns very few nodes or edges is not an error — it reflects the on-chain data.

Common causes:

  • The selected direction does not match the address's activity. An address that only receives funds will produce an empty outgoing trace. Try switching to Incoming or Both.
  • The address has very few transactions within the configured hop depth.
  • The address is a contract with unusual transaction patterns that limit what the trace can follow.

What to do:

  1. Go back to the home page and re-run with a different direction.
  2. If the graph is still sparse, try increasing the hop count.

Trace share links are valid for a limited time. If you follow a shared link and see an expiry notice, the result is no longer available via that URL.

What to do:

  1. If you created the trace yourself, open it from Trace History and generate a new share link.
  2. If someone shared the link with you, ask them to generate a new one.

Trace History Shows a Trace as Expired​

Trace results stored in history have a limited retention period. An expired entry in history means the result data is no longer available.

What to do: Run a new trace for the same address. The address and configuration are shown in the history entry so you can re-run with the same settings.