would be cool if you could link to addr/tx pages with the Details box(es) already expanded, maybe with a #details bit in the URL”

Thanks a lot of sharing I got the client up.

Is there info on connecting it to bitcoin core ( e.g RPC credentials) ? Also would this work with alternative implementation such as btcd, bitcoind ?

from Reddit: https://www.reddit.com/r/bitcoin/comments/ay1b0e/_/ehyfoll

Just a suggestion for the "possibliy coinjoin transactions". Their detection seems to deactivate others privacy notes like the detection of change outputs which are deterministically linked with some inputs. IMHO, it would be a good idea to display this note when such change outputs exist (in addition to the coinjoin detection).

E.g.: https://blockstream.info/tx/8e56317360a548e8ef28ec475878ef70d1371bee3526c017ac22ad61ae5740b8

Like so https://blockstream.info/tx/4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b?expand&theme=light

like from https://github.com/allenpiscitello/liquid-stats

When using copy (address, hash, etc) it would be nice to get some visual clue the data is copied

add confirmation estimation to unconfirmed transactions

Hi.
I cannot find the file(s) that process the blockchain and save it to the database.

Could you please tell me where the processing is done?

Thanks.

While I like the idea of privacy analysis, but done badly it's pretty counter productive. Let's take this:

The alarming "Round payment amount" red warning is dubious at best (we're talking about the difference of 1 significant figure). And the orange "Unnecessary input heuristic" tooltip incorrectly claims that an input is there that is not typically added by wallets (but in reality almost all wallets actually do).

Also not to mention, several of the heuristics are counter-productive. Obviously context-sensitive, but in general it's better for several reasons that wallets are oblivious to creating UIH or not. And likewise creating transactions without change is a good thing (for both fees and privacy).

But probably worst of all, the analysis is missing some of the most important privacy leaking checks.

I think the responsible thing to do would be move "Privacy Analysis" into it's own page that disclaims the limitations of it. Or at least only have prominent warnings for things that are definitely a problem (e.g. address reuse)

Environment:
Ubuntu 18.04.1 LTS

Steps to reproduce:
Followed README...

$ git clone https://github.com/Blockstream/esplora && cd esplora
$ npm install
$ export API_URL=http://localhost:3000/ # or https://blockstream.info/api/ if you don't have a local API server
# (see more config options below)
$ npm start

Also running from the docker command at the same time:

docker run -p 8080:80 \
           --volume $PWD/data_bitcoin_mainnet:/data \
           --rm -i -t esplora \
           bash -c "/srv/explorer/run.sh bitcoin-mainnet explorer"

The line export API_URL=http://localhost:3000/ is confusing because I'm not sure what is supposed to be running on port 3000. netstat -plunt only shows SSH, the explorer front-end running on port 5000, and the explorer API(?) running on port 8080.

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp6       0      0 :::22                   :::*                    LISTEN      -                   
tcp6       0      0 :::5000                 :::*                    LISTEN      28567/node          
tcp6       0      0 :::8080                 :::*                    LISTEN      - 

Even with export API_URL=http://localhost:8080/ I am getting the same results.

What is supposed to be running on port 3000?

Attached is a screenshot of the error page, which is what I see when I navigate to port 5000,

Preview for social share that contain information related: for a tx can show input, output, fee, for a specific output it may show the amount, for blocks we can show total fee + reward, size, etc

When viewing Blockstream.info with Javascript disabled (ie. via Tor Browser), only a blank page is presented.

add transaction timestamp from block for confirmed transactions

see https://developer.mozilla.org/en-US/docs/Web/OpenSearch
and
https://stackoverflow.com/questions/7630144/how-to-add-google-chrome-omnibox-search-support-for-your-site

Do you think there will be a possibility to add such feature with current live infrastructure? Both for Bitcoin and in particular Liquid

I'm not sure if this is intentional for some reason, but other endpoints like address/:address/txs return data with access-control-allow-origin: * headers. The broadcast endpoint does not.

Hi, I've been running Esplora for 2 weeks with Docker. Bitcoin Core sync'ed quickly since I already had the data. Electrs then started working hard but has been using only around 1% of the CPU for several days.

I'm having a look at nginx logs in the container and I can see it's trying to connect to the upstream but the connection is refused when I hit the server. Port 3000 is indeed not a listening port in the container, nor is it on the host.

2019/03/02 03:55:18 [error] 199#199: *224 connect() failed (111: Connection refused) while connecting to upstream, client: 139.28.218.30, server: , request: "GET /api/blocks/tip/height HTTP/1.1", upstream: "http://127.0.0.1:3000/blocks/tip/height", host: "esplora-mainnet:8080", referrer: "http://esplora-mainnet:8080/"

Around 750GB of disk space is used on a total of 1TB.

I haven't changed anything to the configs, except adding -vvv to the supervisord config to know what was going on.

...
2019-03-01T21:42:12.850+00:00 - DEBUG - Starting pre-cache for scripthash 26/10692
2019-03-01T22:48:43.007+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable
2019-03-02T00:39:57.217+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable
2019-03-02T02:15:11.364+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable
2019-03-02T02:15:11.373+00:00 - DEBUG - Starting pre-cache for scripthash 31/10692
2019-03-02T03:25:11.233+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable

It looks fine, I don't see errors anywhere. When is electrs going to listen to port 3000?

Thanks.

Can we add an ID to the transaction details so you can anchor links directly to it? Its great to have an argument to have the detail expanded on landing but it would be great to just land on that point of the scroll too.

Hi,

It seems like the actual default port (on which the front end is running) is 5000 instead of 3000.
https://github.com/Blockstream/esplora#configuration-options

For the API_URL (https://github.com/Blockstream/esplora#developing), it should be pointing to http://localhost:3000/, which is where electrs is listening by default.

Is that correct?

Allow search for multiple addresses, transactions, without having to make multiple request to the api.

Ex: /api/address/3BFvcn3nb86ZUQTekTViTuFpXduvvdcZot,3PDj9uwWjoPjtr18ggfJBCY7Vrnwiac4Me.

You are a public company, so you don't need to hide your location, thus you are in a position to provide a faster, more stable and more reliable Tor hidden service than other services with the following configuration options:

# ---MAKE TOR FASTER---

# Need to disable for HiddenServiceNonAnonymousMode
SOCKSPort 0
# Need to enable for HiddenServiceSingleHopMode
HiddenServiceNonAnonymousMode 1
# This option makes every hidden service instance hosted by a tor
# instance a Single Onion Service. One-hop circuits make Single Onion
# servers easily locatable, but clients remain location-anonymous.
HiddenServiceSingleHopMode 1

explanation of metric here:
https://en.bitcoin.it/wiki/Bitcoin_Days_Destroyed

Since we have a really nice block explorer we might want to cross-link with some information about the Lightning network (which points to Bitcoin on-chain information anyway). I've been collecting some stats over the last months about channel lifetime and node lifetime, and I think it'd be an interesting facette to add to the explorer. We'd only be indexing and displaying publicly available information, and cross-link public channel-events with the matching transactions.

Information

Channel lifetime information

• General channel stats (capacity, % of time enabled, lifetime)
• Cross-link with on-chain events (funding TX, close/sweep transactions, splices)
• Availability plot (disabled vs. enabled)

Node lifetime information

• Node stability metrics
• Channels for a node
• Evolution of various metrics over time (capacity, disabled vs. enabled channels, channel duration)

Running the docker command per the README.md. The result is a page with a 502 Bad Gateway error due to a missing endpoint in /api/blocks/:1 when going to the :8080 web page.

Currently there is no date field when viewing a transaction, please add that so it's easy to see when the transaction was sent.

shesek/electrs@823b68e#r32610980

It would be cool to be able to present blinding key for specific output and look at unblinded values.

Should be possible (although would require porting rangeproof rewind code to js), and would work only with js enabled, will need to load additional js with implementation, etc..

But it could be useful for educational purposes (tutorials linking to real confidential transactions that you can examine with blinding key from tutorial), or for trivial audit, for example.

That would be quite a lot of work, of course, so I am just leaving this idea here, maybe someone somewhen will have time to implement this :-)

For example: https://blockstream.info/address/1VayNert3x1KzbpzMGt2qdqrAThiRovi8

Would be nice for elements/liquid.

It would be nice to display recent timestamps in a more human readable format, like "2 hours ago", "23 minutes ago" or "10 seconds" ago. Especially when looking at recently arrived blocks, it would make it easier to mentally parse the data.

It seems that the timestamp for blocks is always displayed in OS language. It's always English for me, even when I select a different language, and our translator noticed that it's always Korean for him, even when he selects Japanese.

Hi, I just upgraded esplora to the latest version. When clicking on the "Transactions" tab, I am getting this message.

blockstream.info works as expected though. I just rebuilt the esplora container as documented.

Thanks!

We should mark as such uncompressed keys as well as anti fee sniping nlocktime

I was looking for output index 16, and was a bit annoying to count with the details expanded. Just leaving the number in the box somewhere would make this a piece of cake.

add inputs value for coinbase inputs

Example: https://blockstream.info/address/17iyRRXBHJKbv5DKPPkttWewm3CHdNPGQd

scantxoutset "start" "[\"combo(041ada81ea00c11098d2f52c20d5aa9f5ba13f9b583fda66f2a478dd7d95a7ab615159d98b63df2e6f3ecb3ef9eda138e4587e7afd31e7f434cbb6837e17feb0c5)\"]"

{
  "success": true,
  "searched_items": 50244201,
  "unspents": [
    {
      "txid": "540a7e54fd64478554519f1b2d643ecc888c5030631487f9cfc530b71d281309",
      "vout": 0,
      "scriptPubKey": "41041ada81ea00c11098d2f52c20d5aa9f5ba13f9b583fda66f2a478dd7d95a7ab615159d98b63df2e6f3ecb3ef9eda138e4587e7afd31e7f434cbb6837e17feb0c5ac",
      "amount": 50.00000000,
      "height": 50
    },
    {
      "txid": "8efb0be559ea251459184beca257fb36746a6c7464098b1bed2d12bb1383713b",
      "vout": 0,
      "scriptPubKey": "76a91449c0e836a0bb1e176097e6408efe6cb4c11a98f588ac",
      "amount": 0.00100000,
      "height": 410333
    }
  ],
  "total_amount": 50.00100000
}

https://wasabiwallet.io/

I recently pointed Wasabi's website to Blockstream.info and it seems like it says "transaction not found" when the coinjoin is unconfirmed. Currently these three are not found:

c394361f5dbfb01f2a69a2111c36dfb5fe8c8dde0f57a0a5a856a959b2d6ad65
94537ef9853c0641e5220e6f4ffd0b39ba63d847e70175b6c923434a076f2c4c
b293c0e2d4b24bde3ae952fb0f24f9d8af05d9710a61dfb87a82700c2ce6187f

Blockchain.info shows it properly. What can be the issue? Some bitcoind configuration makes you not to show large unconfirmed transactions?

With high security settings the TOR Browser blocks SVG images. That leads to the bitcoin/liquid logo not being shown:

Maybe use a png image for the nojs version?

This issue is a problem I encountered with your electrs fork -- but that repo doesn't accept issues so I'm posting here.

I get an error when I run the build command described in the directions:

$  cargo run --release --bin electrs -- -vvvv --daemon-dir ~/.bitcoin
  Downloaded cc v1.0.25
    ...
   Compiling crossbeam-utils v0.6.1
   Compiling rayon-core v1.4.1
error: failed to run custom build command for `rayon-core v1.4.1`
could not execute process `/mnt/hdd2/electrs/target/release/build/rayon-core-ce94679caf3f5155/build-script-build` (never executed)
warning: build failed, waiting for other jobs to finish...
error: build failed

I can run the same command from the base romanz/electrs project and it builds successfully.

So I don't believe it's an upstream problem. But I lack the rust chops to debug exactly what is failing ...

add server side rendering fallback for NOJS/crawlers/etc

I'd like a way to show only unspent outputs for a specified address. Same format as /address/:address but only unspents.

This is already available in the API (GET /address/:address/utxo) but GUI accessibility would be nice.

Motivation

The Glacier Protocol requires users to manually select UTXOs for withdrawal, printing a QR code with the raw transaction data for each one. Today the process uses blockchain.info, but a few months ago that site removed their "Unspent Outputs" link from the GUI, so Glacier withdrawals are currently somewhat broken.

I can't find an alternative block explorer with similar functionality, but it seems like it would be easy to add to Blockstream.info.

Similar to sites like stackoverflow where you can link a specific answer in a page, could be nice to link directly an input or an output of a tx, the specific input become highlighted.
I imagine this could be done client side, with a link like:
https://blockstream.info/tx/66df7564d51f4ca57c045562fe858e7bfb63a5abe83dfd9c03c7b493531edbb1#i0
which will bring to the transaction page, open details, scroll the page to the input 0, and highlight the input 0

Compare this tx:
https://blockstream.info/testnet/tx/418481174add9bd6af97fe4e4929896ffea62dcbf0a2f3abdb12ec3b7823ff88

With this tx:
https://www.blocktrail.com/tBTC/tx/418481174add9bd6af97fe4e4929896ffea62dcbf0a2f3abdb12ec3b7823ff88

expected from address:
2N4anZTd2Dbwh7K5BWUuDRQu2SBirE7Kybn
found from address:
1d301e5ff39a7f1dbc5b313e5f6d76e7e26800e55f632b59d37aeae26befabea

• Separate mempool and fee estimation with a horizontal spacer

• Add mempool to home page after Broadcast tx

• Have 502 bad gateway similarly rendered as 404 and with a message like "Esplora is currently not available, perhaps it is still loading, please retry again later." - or maybe we could even have some kind of IDB/indexing progress?

• Recent transactions remains populated even mempool is empty, which may be ok but depth wouldn't be applicable anymore?

• Seeing things like "0.00 vMB from tip" is not nice, should we move to vKB or switch to "< 0.01 vMB from tip" ?

• When we suggest about overpaying - should we link to the estimation being used? Same about calculation for segwit/bech32

• Refresh latest transifex languages update (Italian, etc)

ability to explore an x-pub and y-pub (segwit version of x-pub)