Done. @abduraman & @Mike_Wagner sorry for the disappointment 
(Outdated post) Network Explorer
2 Likes
Hello @J053,
It’s possible but it’s not trivial. When you see a “linked transaction” like here that’s because metadata of this transaction contains a “RequestedTxID” value.
I know. You’ll need to make a query to your DB for a trade response with RequestedTxID = TxID. Also, if it was unsuccessful, the query will return 2 TxIDs, because of the tradingFee and sellAmount refund, right?
I don’t run this kind of queries on a table with 1.5+M of rows 
. That’s why I build a specific projection for this kind of use cases.
Yep, example:
2 Likes
No disappointment here. Your contributions to the ecosystem are always superb.
4 Likes
In order to be ready for Privacy V2, I just deployed a test version of Incscan:
This version uses testnet-2 Incognito network and all USD calculations are disabled or faked.
Feel free to use it for all your tests!
5 Likes
Wen ICO? 
2 Likes
I think I found a bug.
For beacons that have a shard with more than 1 block, like this one or this one, the shards that have two blocks (in both the shard 6), are not shown in the Associated Shard Blocks section.
Also, the two blocks of those shards that went into a single beacon height are not accessible.
Blocks in shard 6 I found missing:
1116962, 1116963, 1116891, 1116892, 1116809, 1116810.
1 Like
@J053 Yep, I’m aware of that, Investigation in progress.
Volume calculations are not working because Incscan misses some transactions from missing block shards.
(it’s a new behaviour, it started 2 days ago)
2 Likes
Ok, the real issue is that Incscan doesn’t index shard 6 since block 1112999…
2 Likes
From fullnode logs:
2021-04-03 21:00:08.739 utils.go:89 [ERR] Syncker log : Insert block 1113000 hash [130 206 41 163 231 182 122 235 247 180 152 47 170 213 51 99 14 214 217 177 96 89 26 167 214 149 163 128 186 254 123 103] got error -1051: Instruction Hash Error
Expect instruction hash to be 27fc8ec90bc7f6b9406e99019da1988879300d56e7cc8efae9984040898d98f2 but get 0000000000000000000000000000000000000000000000000000000000000000 at block 1113000 hash 677bfeba80a395d6a71a5960b1d9d60e6333d5aa2f98b4f7eb7ab6e7a329ce82
Instruction Hash Error
github.com/incognitochain/incognito-chain/blockchain.NewBlockChainError
/Users/autonomous/projects/incognito-chain/blockchain/error.go:365
github.com/incognitochain/incognito-chain/blockchain.(*BlockChain).verifyPreProcessingShardBlock
/Users/autonomous/projects/incognito-chain/blockchain/shardprocess.go:325
github.com/incognitochain/incognito-chain/blockchain.(*BlockChain).InsertShardBlock
/Users/autonomous/projects/incognito-chain/blockchain/shardprocess.go:147
github.com/incognitochain/incognito-chain/blockchain.(*ShardChain).InsertBlk
/Users/autonomous/projects/incognito-chain/blockchain/shardchain.go:222
github.com/incognitochain/incognito-chain/syncker.InsertBatchBlock
/Users/autonomous/projects/incognito-chain/syncker/utils.go:83
github.com/incognitochain/incognito-chain/syncker.(*ShardSyncProcess).streamFromPeer
/Users/autonomous/projects/incognito-chain/syncker/shardsyncprocess.go:281
github.com/incognitochain/incognito-chain/syncker.(*ShardSyncProcess).syncShardProcess
/Users/autonomous/projects/incognito-chain/syncker/shardsyncprocess.go:185
runtime.goexit
2 Likes
UNSCHEDULED MAINTENANCE
Incscan fullnode is out of sync. All data related to shard 6 are not indexed/displayed.
All volume calculations are disabled until fullnode is fully back online.
ETA for the fix: TBD
2 Likes
End of maintenance
I temporarily switched Incscan indexing to https://community-fullnode.incognito.org fullnode.
5 Likes
How many PRV?
On the left click on Privacy Coin -> Overview
