Tx hash: 76b49f48a3281cd0cb9ce782f92e1fe31917d6faca80d7a30a5acb23a21a81d7

Tx prefix hash: 76b49f48a3281cd0cb9ce782f92e1fe31917d6faca80d7a30a5acb23a21a81d7
Tx public key: 73eff8e600432637da82fded1129f2015a422215e743b302af7763f4b393f5f4
Timestamp: 1517425723 Timestamp [UCT]: 2018-01-31 19:08:43 Age [y:d:h:m:s]: 02:063:17:14:36
Block: 756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 569700 RingCT/type: no
Extra: 0173eff8e600432637da82fded1129f2015a422215e743b302af7763f4b393f5f4020800000000234f3d56

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: cb78d14d8fd0a691fcfb260b15f35fcd306b76850cc0df5d7f46e9e9d3eca345 0.00200000 138 of 58525
01: 550799dc99a405cae3add022f59225dab029ce4d7f1a1f1bac8ad26d71ed5793 10000.00000000 793 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: