A bug in decoding inputs?
I like the new feature of decoding the inputs. While testing it, I'm confused at interpreting the result. Here's an example where
- tx hash: bfb5bd5553dbdcbe9be81703456497aebc7a6af2fd54bbf1a0012b50ed2bb373
- address: 9svHk1wHPo3ULf2AZykghzcye6sitaRE4MaDjPC6uanTHCynHjJHZaiAb922PojE1GexhhRt1LVf5DC43feyrRZMLXQr3mk
- viewkey: 339673bb1187e2f73ba7841ab6841c5553f96e9f13f8fe6612e69318db4e9d0a

![screen shot 2017-01-20 at 11 13 49 am](https://cloud.githubusercontent.com/assets/1090150/22135453/8ec2cd76-df11-11e6-85a8-10c9095c0245.jpg)

![screen shot 2017-01-20 at 11 14 13 am](https://cloud.githubusercontent.com/assets/1090150/22135455/9484eee2-df11-11e6-867c-968f7ed86c6c.jpg)

Why do I see only two keys under the "output public key" list in each decoded input? Also, the second output key in the first input `57dbf8a7bd816b50daeea054bbed8be39e69cd84db13da9be272f0ba71a945f8` was not in the input ring. Is this due to a bug?