Misleading transaction time when in micro block
See original GitHub issueDescribe the bug A time in the past is shown for transactions in micro blocks
The time does not makes sense as it looks like that the tx is executed at the already confirmed block, more precisely, that the clarity variable block_height
is the height of the confirmed block. This is not true.
To Reproduce Steps to reproduce the behavior:
- Go to https://explorer.stacks.co/transactions?chain=testnet
- See timestamp on microblock
Expected behavior Do not show a transaction time until the block with the block_height used during processing the transaction is confirmed on Bitcoin.
Screenshots
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:15 (2 by maintainers)
Top Results From Across the Web
Microblocks Reduce Transaction Processing Times to Seconds
The Stacks blockchain settles blocks on the Bitcoin blockchain, which averages one block every ten minutes. In order to provide users and ...
Read more >txpool - What is the relationship between block time and the ...
Block time is the time it took for the block to be mined and added to the blockchain. However, the list of transactions...
Read more >What happens to a mined block that contains an invalid ...
A Bitcoin transaction generally needs 6 confirmations from miners before it's processed. The average time it takes to mine a block is 10...
Read more >On Slow and Fast Block Times | Ethereum Foundation Blog
ten minutes, for those ten minutes, and allowing the dictator to produce blocks very quickly.
Read more >Real transaction speed - Protocol Development - Aeternity forum
it is clear to me that aeternity has times as fast as the dash ... I have seen orphan blocks and transactions moving...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Follow up. I see that in the API code, is unanchored is being set to !dbTx.block_hash in db-controller.ts. But as we see in the response, the block_hash is not null, rather, it is
"block_hash": "0x",
@JackNapolitano you’re right, thanks for digging! I’ll get on it ASAP