Timeline for Checking the Merkle Root for Block #100000
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2019 at 13:42 | answer | added | vincenzopalazzo | timeline score: 0 | |
| Sep 17, 2018 at 16:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 13, 2018 at 20:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 8, 2018 at 12:01 | history | tweeted | twitter.com/StackBitcoin/status/1027162944747069440 | ||
| Jul 8, 2018 at 22:34 | answer | added | Ben Stolman | timeline score: 1 | |
| Jan 7, 2018 at 2:11 | comment | added | meshcollider | I doubt there are websites which take bytes input to sha256, best approach is to use python or another language and convert the string to bytes before input to the sha256 | |
| Jan 7, 2018 at 1:35 | comment | added | Adam Smith | Yes, @MeshCollider you are right. Is there a way to easily convert to bytes? | |
| Jan 5, 2018 at 22:14 | comment | added | meshcollider | I suspect you are hashing the transaction ID as a string rather than as bytes | |
| Jan 5, 2018 at 22:09 | comment | added | Pieter Wuille | Perhaps include the intermediate hashes you're getting? That may give people a hint where you went wrong. | |
| Jan 5, 2018 at 22:06 | history | asked | Adam Smith | CC BY-SA 3.0 |