Timeline for Local ethereum node contain two different blocks but with same height
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 8, 2018 at 22:46 | comment | added | Ramesh Pareek | same happened with me. Any solution? or discussion are welcome. email [email protected] | |
| Aug 31, 2017 at 23:58 | comment | added | Ismael♦ | Perhaps it is included as an uncle in another block. | |
| Aug 31, 2017 at 17:54 | comment | added | DeV1doR |
I will receive this one ropsten.etherscan.io/block/1586395. Don't understand, why my local node does not delete orphaned block with hash 0x162ae4b189f77ed65d0be270aa8dea08d4e7dcd70432a7d1fd4e6b0fb1b301d6 (when the valid is 0xa9625a969941619b6a34497dc7b337df95c99378081177ea9a026a6712d266ef)
|
|
| Aug 31, 2017 at 16:57 | comment | added | Ismael♦ |
Calling eth.getBlock(1586395) which block do you get? A chain reorganization should adjust with time.
|
|
| Aug 31, 2017 at 12:56 | comment | added | DeV1doR | Took hashes from local node in testnet. | |
| Aug 31, 2017 at 11:51 | comment | added | Thomas Clowes | Where did you get the hashes from? I assume that there was simply a chain reorganisation. One is part of the longest chain, the other is not. | |
| Aug 31, 2017 at 10:54 | history | asked | DeV1doR | CC BY-SA 3.0 |