Tx hash: 5a288e20132f1f5e0ba80204d8c711ac03f4d55165d5ebd0ad14be118c77c9a9

Tx prefix hash: 5a288e20132f1f5e0ba80204d8c711ac03f4d55165d5ebd0ad14be118c77c9a9
Tx public key: cfcfb0ff2514d8adbcae38c235d0a57f50efb7ad8eba9f409ab36d9bd7d248bc
Timestamp: 1517420640 Timestamp [UCT]: 2018-01-31 17:44:00 Age [y:d:h:m:s]: 02:025:21:00:26
Block: 652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 542612 RingCT/type: no
Extra: 01cfcfb0ff2514d8adbcae38c235d0a57f50efb7ad8eba9f409ab36d9bd7d248bc02080000000fa06035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: bd538dcf0520c1904e756ebaf62a0e417991feb1e7f4872044a3defcb62569e2 0.00200000 72 of 58525
01: 5df18dc818f95401d54e5b7b88b2bb61b52dd9903bd08342c94ed4a43cd7f14f 10000.00000000 687 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: