Tx hash: fa0dd6670516fb7a1a8932725892aa03cfc0535b60fb2272a35265ce6469eba8

Tx prefix hash: fa0dd6670516fb7a1a8932725892aa03cfc0535b60fb2272a35265ce6469eba8
Tx public key: d6bebba25fb27873903d578e11a58c58e32de4c3b79b36685d0f96ec251594c6
Timestamp: 1517412041 Timestamp [UCT]: 2018-01-31 15:20:41 Age [y:d:h:m:s]: 02:024:00:02:47
Block: 442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 541404 RingCT/type: no
Extra: 01d6bebba25fb27873903d578e11a58c58e32de4c3b79b36685d0f96ec251594c602080000000b8b6035b3

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: dbab8ae8156b8da5b2ada86e548ebe8aa6ec14a198501ce7f54b8e40c7e126c6 0.00100000 94 of 60494
01: c78523e6188baf72a9c7fc110b06f9dd8d3c3080e04886e7ccdaade1d1a146a0 10000.00000000 461 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: