Tx hash: 39f3263b90d22ebbd0ee671e8129fe13f48d63c4b1c6128d6cd814c6e17098e6

Tx prefix hash: 39f3263b90d22ebbd0ee671e8129fe13f48d63c4b1c6128d6cd814c6e17098e6
Tx public key: 0db068263392d4898f5060fbb981b6b95075be9e58602feaf38cd93e9e53d6bf
Timestamp: 1517418213 Timestamp [UCT]: 2018-01-31 17:03:33 Age [y:d:h:m:s]: 01:229:07:45:39
Block: 594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 426814 RingCT/type: no
Extra: 010db068263392d4898f5060fbb981b6b95075be9e58602feaf38cd93e9e53d6bf020800000000956035b3

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: a8c5dc957b94c1637b6716259a6b6851c0adb78835a84e07aa62782fd1433f13 0.00100000 162 of 60494
01: aebf5bb1355620843a08bdd2085f3383a914d27bad54025461f1060f867b22a2 10000.00000000 626 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