Tx hash: 02f6beef7a3e08609f567712654dc97915770b7796012c7f81ef0ce89be20db6

Tx prefix hash: 02f6beef7a3e08609f567712654dc97915770b7796012c7f81ef0ce89be20db6
Tx public key: 388b58e21e9a374bf42992230015ee5ec3e11d2a8430b2e43f1b55505df1c8f8
Timestamp: 1517420563 Timestamp [UCT]: 2018-01-31 17:42:43 Age [y:d:h:m:s]: 01:230:23:14:52
Block: 650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 427958 RingCT/type: no
Extra: 01388b58e21e9a374bf42992230015ee5ec3e11d2a8430b2e43f1b55505df1c8f80208000000000fedfc57

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: eacbd7cd3fd986fc72db40c4a5552d7a0ead03eebf7bd89fad6dbc33985c3e97 0.00200000 71 of 58525
01: 4004ff479d3b053ddbe2a384ecdb4f3af1bfdee0b2302d676b92a16e03d8f232 10000.00000000 685 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: 2.1.0.1-master-release