fix(explorer): reduce transaction detail latency - #1229
Merged
Conversation
Bundle Size Report
Chunk changes (>1KB)
Compared against main branch (baseline from 4/27/2026, 4:02:54 PM) |
Contributor
Author
Cloudflare deployment
Production traffic was not changed. |
Bundle Size Report
Chunk changes (>1KB)
Compared against main branch (baseline from 4/27/2026, 4:02:54 PM) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
Receipt and transaction detail routes synchronously fan out across several RPC calls during SSR. In production, the configured
TEMPO_API_KEYmade the higher-latency API passthrough the sole server transport, so its tail latency compounded across dependent request phases. Each SSR request also created a fresh query cache, so immutable transaction data was recomputed on every page load.Cloudflare preview
Mainnet Worker preview
GitHub skipped the normal preview job because the PR author association is
CONTRIBUTOR; this was uploaded manually withwrangler versions upload --env mainnet --preview-alias pr-1229. It is an isolated Worker version and receives no production traffic.Edge benchmarks
Repeated requests include a unique query string to bypass page-level HTTP caching. TTFB includes network latency from the same client. The application cache keys intentionally ignore the query string.
Reported hash
0x003acd00bf113c046de81f1123e16767ee67731eb9b06a4dd154fa82f260d822The transaction response also shrank from about 784KB to 432KB by moving trace and balance-change payloads off the blocking SSR path.
Previously unseen hashes (cold path)
Three recent hashes per route, requested once from each deployment:
The reported receipt's first preview request was approximately tied with production because both paid the upstream cold-path cost. Subsequent requests are served from Cloudflare's immutable-data cache.
Screenshots
No intended visual change; the balance-change panel now shows its existing skeleton state while deferred data loads. The deployed preview was browser-verified to hydrate the full balance updates and trace data with no console warnings or errors.
Verification
pnpm checkpnpm check:typespnpm --filter explorer test --run(124 tests)pnpm precommit