Tx hash: a2b87b97bdf10c6eb78a64cb1f77e1ad89ffa4e1e6839bfbe01b801c02fc5c61

Tx prefix hash: a2b87b97bdf10c6eb78a64cb1f77e1ad89ffa4e1e6839bfbe01b801c02fc5c61
Tx public key: bd56561ee05d0803171650b271b02bbc41a17eed9e58173d74c6b57e5b97844a
Timestamp: 1517417128 Timestamp [UCT]: 2018-01-31 16:45:28 Age [y:d:h:m:s]: 02:063:18:36:13
Block: 569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 569853 RingCT/type: no
Extra: 01bd56561ee05d0803171650b271b02bbc41a17eed9e58173d74c6b57e5b97844a02080000003fd96035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 611c1d8207a80a790e4277c3689d943c63b4d753346cdecf7cce695ab1bc21f4 0.00200000 37 of 58525
01: 658730056e2399b39279fadcb202b60a158d3b04c5587eef25b3f440d1818eff 10000.00000000 601 of 3008

Check which outputs belong to given BitTube address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are NOT sent to the server, as the calculations are done on the client side



Prove to someone that you have sent them BitTube in this transaction

Tx private key can be obtained using get_tx_key command in bittube-wallet-cli command line tool
Note: address/subaddress and tx private key are NOT sent to the server, as the calculations are done on the client side



More details
source code | explorer version (api): master-2019-07-08-dbc4cc2 (1.1) | BitTube version: 2.1.0.1-master-release