Tx hash: 16020a35cffd47fd6086643873ddcb2e761fc3fa43be87de7fe8266075e1793e

Tx prefix hash: 16020a35cffd47fd6086643873ddcb2e761fc3fa43be87de7fe8266075e1793e
Tx public key: 9026ac111d652868259e7bc8125ecc9639307d9743ef84e89b383b5e9cf58917
Timestamp: 1517418398 Timestamp [UCT]: 2018-01-31 17:06:38 Age [y:d:h:m:s]: 01:227:00:46:25
Block: 600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 425179 RingCT/type: no
Extra: 019026ac111d652868259e7bc8125ecc9639307d9743ef84e89b383b5e9cf5891702080000000071bcde02

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 49d0cea03ee1aaae60eb56ead842c5944b8f93ac97ccab8aeaf879beae3839ba 0.00100000 163 of 60494
01: 9b861449c4c408a85e1037408f3f7f85d651a2ed80562047c189909678b9975e 10000.00000000 632 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