Tx hash: 506d05f843f50ca57151657c73d145cf8e542675e5518240e985c0b84f7567cb

Tx prefix hash: 506d05f843f50ca57151657c73d145cf8e542675e5518240e985c0b84f7567cb
Tx public key: 1149d4173bf1385aba9634a1f54c20e8be4999a92f73c7cd5aed4a4e209e3528
Timestamp: 1517427699 Timestamp [UCT]: 2018-01-31 19:41:39 Age [y:d:h:m:s]: 01:233:14:28:04
Block: 801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1250 kB
Tx version: 1 No of confirmations: 429755 RingCT/type: no
Extra: 011149d4173bf1385aba9634a1f54c20e8be4999a92f73c7cd5aed4a4e209e352802080000002ddf6035b3

2 output(s) for total of 10000.10000000 TUBE

stealth address amount amount idx
00: c98c2c95424a6a2b50cd08edac463ad90baceb1a5f0344971b634dda6e119060 0.10000000 1541 of 435186
01: 5728f021911a1f6389cff363edbb8236590063e3b8c500937922a914596a29e6 10000.00000000 839 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: