Tx hash: eda3172257563e712e4b3c7f42e7a2092c5dd576db4982e8512112688c2689c6

Tx prefix hash: eda3172257563e712e4b3c7f42e7a2092c5dd576db4982e8512112688c2689c6
Tx public key: 88357df2c963a6754cff2b65e98491b15b1c60205c4e56878de718165f090fd4
Timestamp: 1517405668 Timestamp [UCT]: 2018-01-31 13:34:28 Age [y:d:h:m:s]: 01:046:17:58:22
Block: 217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 296198 RingCT/type: no
Extra: 0188357df2c963a6754cff2b65e98491b15b1c60205c4e56878de718165f090fd4020800000000010b68b0

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 8f021b17d6db05291b1b8396f663b422e63a7bbe6ba682d5b598f1472b90598b 0.00100000 21 of 60492
01: d9b5e01ebbca35955e346fb86592c3e587a1cb3c7a163105988929c3070d4c32 10000.00000000 227 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-01-31-3693d4a (1.1) | BitTube version: