xinfinorg / xdcscan

Deprecated version of Explorer

XDCScan Explorer

Local installation

Clone the repo

Download Nodejs and npm if you don't have them

Install dependencies:

npm install

Install mongodb:

MacOS: brew install mongodb

Ubuntu: sudo apt-get install -y mongodb-org

Run:

The below will start both the web-gui and sync.js (which populates MongoDB with blocks/transactions). npm run dev

You can leave sync.js running without app.js and it will sync and grab blocks based on config.json parameters node ./tools/sync.js

First you have to run the following to update the current database: fill_token_holders is for update holders to DB when it partially synced and does not want to delete data and resync node ./tools/fill_token_holders.js

sync_all_contract_from_token_transfer is for update contracts that not synced yet for better experience and it will be writting some additional infomation when sync or patcher run to specific block node ./tools/sync_all_contract_from_token_transfer.js

xdcscan's Issues

CSV File introduction

Hi there
There is no way you get your XDC transaction details through CSV File, so could you please provide that option through Explorer, as it's very important for tax file purpose.
Thanks

Token transfer to Metamask wallet not recorded in Blocksscan

Hi,

I am tracing this transfer from Bitrue to Metamask wallet that is not reflected in @blocksscanio. Pls advise what could have been wrong with this transaction.

Thanks.

Belle

TXID: 0xebc463ce51412893c92c530e99e2871e19cc082b3fc014dc1aff51f63b162a16

Metamask Wallet Address: 0x5f56D2edE303B354C00274F72b17c10436Db096a

Metamask Screenshots

Bitrue Screenshot

Testnet compilation does not work

When I tried to verify my code on the testnet explorer, the compilation did not complete and it got stuck. Tried multiple times but it failed to succeed everytime.

It run failed!

npm run dev :

npm run dev

[email protected] dev /var/node/xdc/XDCScan
concurrently "nodemon tools/sync.js " "nodemon app.js"

[0] [nodemon] 1.19.4
[1] [nodemon] 1.19.4
[1] [nodemon] to restart at any time, enter rs
[1] [nodemon] watching dir(s): .
[1] [nodemon] watching extensions: js,mjs,json
[1] [nodemon] starting node app.js
[0] [nodemon] to restart at any time, enter rs
[0] [nodemon] watching dir(s): .
[0] [nodemon] watching extensions: js,mjs,json
[0] [nodemon] starting node tools/sync.js
[1] config.json found.
[0] config.json found.
[0] Connecting ws.apothem.network:8555...
[1] config.json found.
[1] wss://ws.apothem.network WSURL
[1] Connecting https://rpc.apothem.network...
[1] Web3 connection established
[1] config.json found.
[1] (node:16241) Warning: Accessing non-existent property 'getLatestBlocks' of module exports inside circular dependency
[1] (Use node --trace-warnings ... to show where the warning was created)
[1] Express server listening on port 3000
[0] Web3 Provider connected!
[0] Checking for missing blocks
[0] Starting Full Sync
[0] Old block found. Starting block number = 23205760
[0] Quiet mode enabled
[0] Syncing chain from #23205760 -> #23205660
[1] TypeError: Cannot read property 'XDC' of undefined
[1] at getQuote (/var/node/xdc/XDCScan/tools/price.js:28:37)
[1] at processTicksAndRejections (internal/process/task_queues.js:95:5)
[0] Syncing chain from #23205660 -> #23205560
[0] Patching from #23209125 to #23210401
[0] [ - ] Lost connection to the web3 RPC or WS, reconnecting... Socket Error: undefined EPIPE
[0] [ listenBlocks ] error: Error: CONNECTION ERROR: The connection got closed with the close code 1006 and the following reason strin g Socket Error: undefined EPIPE
[0] [ syncChain ] Web3 is not connected. Retrying connection shortly...
[0] [ runPatcher ] Web3 is not connected. Retrying connection shortly...
[0] [ listenBlocks ] Web3 is not connected. Retrying connection shortly...
[0] Web3 Provider connected!
[0] Checking for missing blocks
[0] Starting Full Sync
[0] Old block found. Starting block number = 23205760
[0] Quiet mode enabled
[0] Syncing chain from #23205760 -> #23205660
[0] Syncing chain from #23205660 -> #23205560
[0] Patching from #23209125 to #23210404
[0] Syncing chain from #23205560 -> #23205460
[0] [ - ] Lost connection to the web3 RPC or WS, reconnecting... Connection dropped by remote peer.
[0] [ listenBlocks ] error: Error: CONNECTION ERROR: The connection got closed with the close code 1006 and the following reason strin g Connection dropped by remote peer.
[0] [ syncChain ] Web3 is not connected. Retrying connection shortly...
[0] [ runPatcher ] Web3 is not connected. Retrying connection shortly...
[0] [ listenBlocks ] Web3 is not connected. Retrying connection shortly...
[0] Web3 Provider connected!
[0] Checking for missing blocks
[0] Starting Full Sync
[0] Old block found. Starting block number = 23205741
[0] Quiet mode enabled
[0] Syncing chain from #23205741 -> #23205641
[0] Syncing chain from #23205641 -> #23205541
[0] Patching from #23209125 to #23210407
[0] Syncing chain from #23205541 -> #23205441
[0] [ - ] Lost connection to the web3 RPC or WS, reconnecting... Connection dropped by remote peer.
[0] [ listenBlocks ] error: Error: CONNECTION ERROR: The connection got closed with the close code 1006 and the following reason string Connection dropped by remote peer.
[0] [ syncChain ] Web3 is not connected. Retrying connection shortly...
[0] [ runPatcher ] Web3 is not connected. Retrying connection shortly...
[0] [ listenBlocks ] Web3 is not connected. Retrying connection shortly...
[0] Web3 Provider connected!
[0] Checking for missing blocks
[0] Starting Full Sync
[0] Old block found. Starting block number = 23205724
[0] Quiet mode enabled
[0] Syncing chain from #23205724 -> #23205624
[0] Syncing chain from #23205624 -> #23205524
[0] Syncing chain from #23205524 -> #23205424
[0] Patching from #23209125 to #23210410
[0] [ - ] Lost connection to the web3 RPC or WS, reconnecting... Socket Error: undefined EPIPE
[0] [ listenBlocks ] error: Error: CONNECTION ERROR: The connection got closed with the close code 1006 and the following reason string Socket Error: undefined EPIPE
[0] [ syncChain ] Web3 is not connected. Retrying connection shortly...
[0] [ runPatcher ] Web3 is not connected. Retrying connection shortly...
[0] [ listenBlocks ] Web3 is not connected. Retrying connection shortly...
[0] Web3 Provider connected!
[0] Checking for missing blocks
[0] Starting Full Sync
[0] Old block found. Starting block number = 23205687
[0] Quiet mode enabled
[0] Syncing chain from #23205687 -> #23205587
[0] Syncing chain from #23205587 -> #23205487
[0] Patching from #23209125 to #23210413
[0] Syncing chain from #23205487 -> #23205387
[0] [ - ] Lost connection to the web3 RPC or WS, reconnecting... Socket Error: undefined EPIPE
[0] [ listenBlocks ] error: Error: CONNECTION ERROR: The connection got closed with the close code 1006 and the following reason string Socket Error: undefined EPIPE
[0] [ syncChain ] Web3 is not connected. Retrying connection shortly...
[0] [ runPatcher ] Web3 is not connected. Retrying connection shortly...
[0] [ listenBlocks ] Web3 is not connected. Retrying connection shortly...
[0] Web3 Provider connected!
[0] Checking for missing blocks
[0] Starting Full Sync
[0] Old block found. Starting block number = 23205663
[0] Quiet mode enabled
[0] Syncing chain from #23205663 -> #23205563
[0] Syncing chain from #23205563 -> #23205463
[0] Patching from #23209125 to #23210416
[0] Syncing chain from #23205463 -> #23205363
[0] [ - ] Lost connection to the web3 RPC or WS, reconnecting... Connection dropped by remote peer.
[0] [ listenBlocks ] error: Error: CONNECTION ERROR: The connection got closed with the close code 1006 and the following reason string Connection dropped by remote peer.
[0] [ syncChain ] Web3 is not connected. Retrying connection shortly...
[0] [ runPatcher ] Web3 is not connected. Retrying connection shortly...
[0] [ listenBlocks ] Web3 is not connected. Retrying connection shortly...
[0] Web3 Provider connected!

mongo --version

MongoDB shell version v4.0.26
git version: f12d07945bd82ff9b6726aa74b84ea4e94b06171
OpenSSL version: OpenSSL 1.1.1 11 Sep 2018
allocator: tcmalloc
modules: none
build environment:
distmod: ubuntu1804
distarch: x86_64
target_arch: x86_64

Feature Request: Make "Verify and Publish" feature available via API

Summary of the request: Other block scanner services have successfully provided a verification tool available via API (i.e., Etherscan). It allowed the community to develop tools and plugins like truffle-verify-plugin, which makes the verification process a much less time-consuming task for developers, thus, improving the development experience.

Following this reasoning, I believe it would be a great addition to the Blockscan API, an endpoint that allows users to use the verification feature through an API call.

Founfing search error and there is some time delay in explorer to saw transactions

@BlocksScanIO

I am getting an error message when I searched my wallet address in the search box and I am also facing some time delay in txs history.