I've spent all day trying to figure this out, to no avail.

I'm trying to find a way to analyze the ongoing pending transactions at certain times in the day/week, to ascertain ideal times for processing transactions based on network load, at least based on averages. Specifically, I would like to be able to easily view and ideally download the list of pending transactions currently being broadcast to the network that have not yet been mined, in JSON format for instance, so that I can then analyze that data.

A great example of this would be this page.

However, it does not give me all of the data I am looking for on that initial screen/list, unlike some of the other API calls that they support. Unfortunately there does not seem to be an API call yet for the pending transactions list, otherwise that would be exactly what I need.

This is an example of a supported API call that DOES give me what I need, except I need the same thing for pending transactions.

I am pretty desperate to get this to work for my small project at this point, and will donate/contribute what feeble fraction of ETH I can to anyone who can help me solve this.

2 Answers 2


Geth exposes a nonstandard API to query contents of the txpool (which is equivalent to Bitcoin mempool). See here.


You could take a look at the APIs supplied by BlockCypher, specifically the API for returning a list of unconfirmed transactions:


I think in this case unconfirmed == pending...

  • 1
    Thank you for your reply. I took a look at this, but it does not really seem to be accurate to what is actually pending on the network: api.blockcypher.com/v1/eth/main/txs More specifically, there are about 230 transactions pending at the moment but that only returns 10 results. But this is very close to what I need, if it listed all transactions!
    – Chris P
    Jun 11, 2017 at 9:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.