sickpig / bch-rpc-explorer Goto Github PK

Noticed first on a fork of this repo

https://chipnet.chaingraph.cash/tx/ddec4b40f4eccc239899092bdd1888a1f8cf0ad52585f56d71648d753acc9fea

the explorer doesn't display the data(utf-8) correctly: it doesn't say 'BCMR' it only says ' R'

So the first 3 characters of any opreturn message seem to be dropped somehow by accident. Reproduced this a few times.

see:

https://explorer.bitcoinunlimited.info/address/bitcoincash:qruy37sy0f4nl4nv64gw2lse6vamzapl4vcwv5rq9d

I see this explorer is hosted by many. I wonder if it's possible to add SLP support to it.
Thank you

The UTXO state is our most important metric since it's the scaling bottleneck and also can be a surrogate for our number of holders count, however I haven't found a good place where to watch its stats.

For BTC, I found that there is this: https://www.blockchain.com/es/explorer/charts/utxo-count but they don't have the same chart for BCH.

Suggestion:

• Chart showing (time, utxo count)
• Chart showing (time, total utxo state size)
• Chart showing (time, median utxo size)

Description
Maybe you should update from upstream? And get all the latest upstream improvements and features in your version as well.

Screenshots

869 commits behind:

Regards,
Melroy van den Berg

Like we do for flipstarter and voter.cash transactions, we can identify AnyHedge transactions.

This is possible to parse from a transaction (quoting @rkalis from AnyHedge telegram):

Let me put it in pseudocode.

From the parsed tx, you have:

hedge payout satoshis
long payout satoshis
settlement price
funding transaction (outpoint)

From that you get:

total contract satoshis = hedge payout satoshis + long payout satoshis
hedge USD payout = (hedge payout satoshis / 1e8) * settlement price
long USD payout = (long payout satoshis / 1e8) * settlement price

By definition:

hedge USD payin = hedge USD payout

Then you look up the funding transaction's block timestamp (1 rpc call).
Then you look up the approximate BCH price at the time of funding (e.g. coingecko API). Note that this is an approximation, because we cannot know the exact price used in the contract funding.

From there you calculate:

approx hedge payin satoshis = (hedge USD payin / approx funding price) * 1e8
approx long payin satoshis = total contract satoshis - approx hedge payin satoshis
approx long USD payin = (approx long payin satoshis / 1e8) * approx funding price

From there you can calculate the long's approx profit/loss in terms of sats, $ or %.

Does that make sense? So it should be 1 rpc call + 1 price api call

We don't need to provide all that info, but that is what is possible.

I'm missing spent and received amounts when looking-up a BCH address.

You only see the balance. Would be nice to see the balance with the dollar value and separate spent and received amounts.

Example:

Regards,
Melroy van den Berg

When using bchd, I get resolution failure when using the default seed.bch.loping.net address for peer lookup. See gcash/bchd#436

https://dnssec-analyzer.verisignlabs.com/seed.bch.loping.net

https://dnsviz.net/d/seed.bch.loping.net/dnssec/

In transaction details view, these two properties that do not make sense in a public block explorer context and will never be checked. That is, unless that node running the block explorer is your wallet.

• Is Mine ❌
• Is watch-only ❌

the custom range for block stats and mining summary should maybe have some limit. it will let me enter 0 and 500000. which looks like it would take 4 hours to finish if every 1000 block fetch takes as long as the first 1000 did

Per the fulcrum get_balance method, BCH balance on "token" addresses will only be shown if version is >1.5. This has led to results such as https://chipnet.imaginary.cash/address/bchtest:pzn85ff863dnceq0gt5sd88e00afchyur5jasutc0s?sort=desc&limit=10&offset=10 where BCH balances on token'd UTXOs are excluded, and the overall balance is shown as zero.

I don't know where it is, but since token support is added the explorer should be able to report a version of 1.5.0 and make Fulcrum report BCH balance on tokens again.

Error when using the new CashToken format with token support I get the following error from the explorer:

/root/bch-rpc-explorer/views/address.pug:88
    86| 								div.col-md-6
    87| 
  > 88| 									if (addressObj.hash)
    89| 										if (addressObj.hash && !(addressObj.hasOwnProperty("isCashAddr")))
    90| 											div.row
    91| 												div.summary-split-table-label Hash 160

Cannot read properties of undefined (reading 'hash')

It works for the standard cashaddress:
https://chipnet.chaingraph.cash/address/qry77fz5ph8supxplr57h6lfx0jlw5kxjck0t4wpat

but not for the new format for the same address:
https://chipnet.chaingraph.cash/address/zry77fz5ph8supxplr57h6lfx0jlw5kxjc39ctq8zc

I think something like this:

• 1 more index (tokenID, utxo)

UX:

• list of utxos for a given tokenID
• list of addresses holding some tokenID utxos
• show token data as distinct fields instead of as part of locking script (like when looking at a transaction)

Applies to Nexa explorer fork just the same (group tokens)

Originally posted by @woahdy in blockparty-sh/slp-explorer#413 (comment)

The blocks page has a column for the exact time of a block (it has a Date column, which shows time in MM/dd hh:mm format, with a full yyyy-MM-dd hh:mm:ss format in a tooltip)

The home page has only a counter for "how much time has passed since the that block".

It would be useful to see the exact time of blocks from the home page directly, maybe in a tooltip like in the blocks page.

Thanks in advance!

"5794effa9731c70e36a84eab9a5de7566e22e7efe30eb4b1b91c0717291dce82"

Originally posted by @woahdy in blockparty-sh/slp-explorer#413 (comment)

on /mining-summary if i enter a custom range that is outside the blockchains current tip the page seems like it is hanging.

it does not show an error. and does not let you select any other block range. you also cannot select one from the preconfigured selection. you can either enter a new range in the boxes in order to go back to the block range buttons i need to refresh the page.

this happens for both numbers > tip.height and numbers < 0

can we have a clickable bip21 link next to the QR code on the address detail page pls?
it would make tip bot usage lot easier

"5794effa9731c70e36a84eab9a5de7566e22e7efe30eb4b1b91c0717291dce82"

Originally posted by @woahdy in blockparty-sh/slp-explorer#413 (comment)

dac8d0126697f1d64220315fd747e9c21a9b0af9822463df0c8f9edf80c57de4

Originally posted by @woahdy in blockparty-sh/slp-explorer#413 (comment)

I suggest accepting low-fee transactions to the mempool for the block explorer.

Today I was hit by a bug in Copay that created a transaction that was 1 satoshi short of 1sat/byte. The only explorer that had said transaction was blockchair, and thanks to that I could figure out why my transaction was not confirming.

So, do the same and if possible also add a note that the transaction is low fee to help people than run into the same issue diagnose why their tx isn't confirming.

"dac8d0126697f1d64220315fd747e9c21a9b0af9822463df0c8f9edf80c57de4"

Originally posted by @woahdy in blockparty-sh/slp-explorer#413 (comment)

Describe the bug

A clear and concise description of what the bug is.

Environment (please complete the following information):

• Bitcoin Core / Node Version [e.g. 0.16.3]
• NodeJS Version [e.g. 9.x]
• Browser [e.g. chrome, safari]
• Code Version / Commit [e.g. ab6cde8]

Configuration file content

Please include the content from the following files. BE SURE TO MODIFY YOUR CREDENTIALS BEFORE SUBMITTING!!!

• bitcoin.conf
• Your btc-rpc-explorer environment configuration (either $WORKING_DIR/.env or ~/.config/btc-rpc-explorer.env)

To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots or Log Output

If applicable, add screenshots or log output to help explain your problem.

Additional context

Add any other context about the problem here.

page under the Last Send / Receive column it says text-monospace for every entry

nit: the unit of time is also never indicated