<p>The issue was with how the transactions are sorted. The balance was being calculated with 9c8f1b918e6a6a2 being sorted before 46d529d722d1 (which is incorrect) despite them being ordered correctly in the json. Regardless it should be fixed now.</p>

CC BY-SA 3.0
2015-01-01T19:36:50.033Z
I can see it's now working, and take a look at
http://bitref.com/15PFsB56YYXwXSW6byaxHXfgGz2ySWnDzN
They use this API, now it is sorted as well at their table
Haddar Macdasi
CC BY-SA 3.0
2014-12-31T19:16:26.100Z
2014-12-31T19:16:26.100Z
Kevin
<p>Calling </p>

<pre><code>https://blockchain.info/multiaddr?cors=true&amp;active=15PFsB56YYXwXSW6byaxHXfgGz2ySWnDzN
</code></pre>

<p>I get a json response which I can not figure out if it has some sort of error or that I'm mistaken.</p>

<p>The response show results in transaction 1206412 = 0.01206412BTC added to balance 0BTC should get 1206412 = 0.01206412BTC, however we get balance = 1201206412 = 12.01206412BTC, I think it's error in blockchain.info api or could you explain how the balance is calculated. </p>

<p><img src="https://i.sstatic.net/Qrr6r.png" alt="blockchain response"></p>

<blockchain.info>
How does blockchain.info api works?
Haddar Macdasi
# How does blockchain.info api works?

(Asked by: username_0 on 2014-12-31)

Calling

```
https://blockchain.info/multiaddr?cors=true&active=15PFsB56YYXwXSW6byaxHXfgGz2ySWnDzN

```

I get a json response which I can not figure out if it has some sort of error or that I'm mistaken.

The response show results in transaction 1206412 = 0.01206412BTC added to balance 0BTC should get 1206412 = 0.01206412BTC, however we get balance = 1201206412 = 12.01206412BTC, I think it's error in blockchain.info api or could you explain how the balance is calculated.

![blockchain response](https://i.sstatic.net/Qrr6r.png)

**Tags:** blockchain.info


---

## 1 answers

### Answer by username_1 on 2014-12-31. Score: 2 | Accepted answer

The issue was with how the transactions are sorted. The balance was being calculated with 9c8f1b918e6a6a2 being sorted before 46d529d722d1 (which is incorrect) despite them being ordered correctly in the json. Regardless it should be fixed now.

> **Comments:**
> **username_0**: I can see it's now working, and take a look at http://bitref.com/15PFsB56YYXwXSW6byaxHXfgGz2ySWnDzN They use this API, now it is sorted as well at their table  

---

