Tx hash: ca65c75418b42050e0a3b5d808fefb690c31a6b419e17e9f339ec83b84110d5a

Tx prefix hash: ca65c75418b42050e0a3b5d808fefb690c31a6b419e17e9f339ec83b84110d5a
Tx public key: 638dedfbbfb1170fd0b1a229c5e62f84dcfb8c795de7b69e464f766fbdc87228
Timestamp: 1517418433 Timestamp [UCT]: 2018-01-31 17:07:13 Age [y:d:h:m:s]: 01:205:16:23:30
Block: 603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 409872 RingCT/type: no
Extra: 01638dedfbbfb1170fd0b1a229c5e62f84dcfb8c795de7b69e464f766fbdc87228020800000000b66035b3

2 output(s) for total of 10000.02000000 TUBE

stealth address amount amount idx
00: b561391d50234b834b0514de52d85642f94329e766dc2052c5838ea896c19989 0.02000000 44 of 151559
01: d3f77a6febe3ea0e1dbe2d6eadd800ed66fe924fce68c291a836765c25fb4273 10000.00000000 635 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