Tx hash: 9e256da0a377aae9476bd107cdf6d84eee3d1030c733bf7101daac631ec09471

Tx prefix hash: 9e256da0a377aae9476bd107cdf6d84eee3d1030c733bf7101daac631ec09471
Tx public key: 0cbc705ab2a39a5fd02a0a2e4e9dbb0d12228f7d1b3034b90f360ee16bc3c7f7
Timestamp: 1517411864 Timestamp [UCT]: 2018-01-31 15:17:44 Age [y:d:h:m:s]: 02:023:22:59:01
Block: 434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 541384 RingCT/type: no
Extra: 010cbc705ab2a39a5fd02a0a2e4e9dbb0d12228f7d1b3034b90f360ee16bc3c7f7020800000000126035b3

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 01925837d54c68d9a3ddcd6e9bfbb012eb5d8636dadd5f646804613be713d876 0.00100000 91 of 60494
01: 83eedeeaaff60803c7e164beeac4d16b78ab824f0a4cb8151e1db1b327a642a2 10000.00000000 450 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: