Tx hash: 4ffda15ce5c119b0c83689c283f8a851818dab5e8fdce0fa79e3095c426fbdca

Tx prefix hash: 4ffda15ce5c119b0c83689c283f8a851818dab5e8fdce0fa79e3095c426fbdca
Tx public key: 8cc1aa6878a247c8b634b9c4dc4e7bd7f0308db95f50464d24e1c6084a4c2024
Timestamp: 1517427613 Timestamp [UCT]: 2018-01-31 19:40:13 Age [y:d:h:m:s]: 01:232:18:21:25
Block: 799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 429167 RingCT/type: no
Extra: 018cc1aa6878a247c8b634b9c4dc4e7bd7f0308db95f50464d24e1c6084a4c202402080000000003e84694

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 8e684e9ff33d43e0d007634b7b90b5fb61662772fec8dbf460dd3a82cf4b6773 0.00100000 264 of 60494
01: 048ac7abd700d3c836098c4ab05286c5023e8538bf39e46c2ebb8bb879b25c0d 10000.00000000 837 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: