Tx hash: 4c88ab658bf82abab602c4e3f974d98bf6bf2ae18d688446ac0cbe4b67cb6047

Tx prefix hash: 4c88ab658bf82abab602c4e3f974d98bf6bf2ae18d688446ac0cbe4b67cb6047
Tx public key: 54d3cad7a5c758cb7f2b02bb0a32c036f99de0ab4a886a164b36815abb84c2e9
Timestamp: 1517405766 Timestamp [UCT]: 2018-01-31 13:36:06 Age [y:d:h:m:s]: 01:115:07:48:21
Block: 222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 345390 RingCT/type: no
Extra: 0154d3cad7a5c758cb7f2b02bb0a32c036f99de0ab4a886a164b36815abb84c2e9020800000000019e1704

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: ec0604a339ecd330280af311efe254b7ae473410886ca6c84eaab0f096365f5d 0.00100000 23 of 60493
01: ce4772829b07d589ec082394861838bc0514af7baa8f93f81a6f6c574ea92fb2 10000.00000000 232 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-01-31-3693d4a (1.1) | BitTube version: 2.1.0.0-master-release