Tx hash: 9cf4a589f004c11c2ffc0c2368551b04ed9c76d81db86990c265099e2569ebd7

Tx prefix hash: 9cf4a589f004c11c2ffc0c2368551b04ed9c76d81db86990c265099e2569ebd7
Tx public key: b3cc1afacf86d42736c56b079bcb08d1cdf3cb437856d3493d3bae2e4dcbc9c3
Timestamp: 1517422670 Timestamp [UCT]: 2018-01-31 18:17:50 Age [y:d:h:m:s]: 01:315:10:25:30
Block: 688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 488494 RingCT/type: no
Extra: 01b3cc1afacf86d42736c56b079bcb08d1cdf3cb437856d3493d3bae2e4dcbc9c30208000000005a0b68b0

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 42e1c914a46a9b3850106e69b9e427c5b2a511e67dbd111fb61578827d292c35 0.00200000 86 of 58525
01: 1c0bfd8bdacd0c8e90b8cc3ea07ee54648b50109a3050f7c386cc2a1f8a44362 10000.00000000 724 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