Block explorer (tinyscan) #19
Merged
Conversation
This file contains 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
dag: add GetEpochById statemachine: add GetState
|
. |
explorer: add account.txs explorer: add tx.status, tx.confirmed_in_blocks
db: make migrations more robust, add functions for version and migrate
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I built a really simple block explorer for tinychain, gonna call it tinyscan.
Tinyscan is basically a Golang web server, using the built-in go templating engine, that minimally relies on the BlockDAG and StateMachine types to provide a basic view into the blockchain.
It doesn't require any custom RPC, it just uses the SQLite database.
To run:
Screenshots.
Bugs.
It appears like we're missing some state being processed? ie. http://0.0.0.0:9000/transactions/5fa1c5ae3e7dfcf29d9f73db92004558b81de5f4b3660467e8a1aa8f32c8b46c this transaction which was manually sent by brian is not coming up with any balance for the to account. Not showing up in the ledger table either.
Added "confirmed in" functionality. Turns out this tx was just reorged out.
GetLongestChainHashListhasn't been updated to track the full tip vs. headers tip distinction. As such, the latest block is not found in the /blocks/ index of the longest hash chain.