Tx hash: 439c6c6a50e6c070867a653c70098bd0d53e6572178c4530b421ffed29a38731

Tx prefix hash: 439c6c6a50e6c070867a653c70098bd0d53e6572178c4530b421ffed29a38731
Tx public key: 3f83cc78cfcbcd802d713ef012bbb4c718671e2ae6ad1be8f615bb13b2b95f86
Timestamp: 1517420471 Timestamp [UCT]: 2018-01-31 17:41:11 Age [y:d:h:m:s]: 02:025:20:40:11
Block: 647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 542605 RingCT/type: no
Extra: 013f83cc78cfcbcd802d713ef012bbb4c718671e2ae6ad1be8f615bb13b2b95f86020800000000276035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 52b46a6785d4e74af5e432aef7b57dee66c81bd09cd17d8104b3cacf4f0d2599 0.00200000 70 of 58525
01: 5745b92b8b2ed30451753166ac7ce7518c93af4ce272be3e16a620055995b9e3 10000.00000000 682 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: