fix(explorer): add block_timestamp to /api/address endpoint#470
Open
fix(explorer): add block_timestamp to /api/address endpoint#470
Conversation
Bundle Size Report
Compared against main branch (baseline from 1/16/2026, 2:07:18 AM) |
Cloudflare Deployments
|
This adds the block_timestamp field to transaction data returned by the /api/address endpoint. The app's activity heatmap relies on this field to display transaction timestamps correctly. Without this field, all transactions appear in the most recent bucket since the timestamp defaults to undefined.
o-az
force-pushed
the
fix/explorer-block-timestamp
branch
from
0341d00 to
108554e
Compare
o-az
approved these changes
Jan 17, 2026
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
Adds the
block_timestampfield to transaction data returned by the/api/addressendpoint.Problem
The app's activity heatmap relies on this timestamp field to display transaction times correctly. Without it, the IndexSupply API returns Unix timestamps in seconds as strings, but since the endpoint wasn't including
block_timestampin the select query, all transactions appeared in the most recent bucket (timestamp defaulted to undefined).Changes
block_timestampto the select fields in the txs querytimestampfield in the response object (Unix seconds as string)Testing
Type checks pass. The app will be able to parse these timestamps using
Number(txInfo.timestamp) * 1000to convert from Unix seconds to JavaScript milliseconds.