Tx hash: 5e3385c0ce60730eb7ab06815ca1b5d2fb0f30c993af174114a14272f6aa009e

Tx prefix hash: 5e3385c0ce60730eb7ab06815ca1b5d2fb0f30c993af174114a14272f6aa009e
Tx public key: ad2d12e163f0246d97b86d9fbfd3018cc75bbe31fecb63688cd7839ef1e2e761
Timestamp: 1517411924 Timestamp [UCT]: 2018-01-31 15:18:44 Age [y:d:h:m:s]: 02:023:23:07:08
Block: 437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 541386 RingCT/type: no
Extra: 01ad2d12e163f0246d97b86d9fbfd3018cc75bbe31fecb63688cd7839ef1e2e7610208000000086a6035b3

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: a92a6d8b6de0d77a625ae5a1d4970e0eed85d215180dfb994361e42df0404a25 0.00100000 93 of 60494
01: c189f7641fd0d410c3de2be84496d3771d7bcf826da34eeda74cd922b409efc2 10000.00000000 454 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: