Tx hash: c0685e66afce8c1bf84a1a94f94b45281a689d9c80272de33e8a2fd55a65dd62

Tx prefix hash: c0685e66afce8c1bf84a1a94f94b45281a689d9c80272de33e8a2fd55a65dd62
Tx public key: 16ec4eb3b64374762caae1de0d11258d6f46d09558dd80ca1b75e85fc91b921b
Timestamp: 1517418603 Timestamp [UCT]: 2018-01-31 17:10:03 Age [y:d:h:m:s]: 01:291:06:32:40
Block: 609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 471205 RingCT/type: no
Extra: 0116ec4eb3b64374762caae1de0d11258d6f46d09558dd80ca1b75e85fc91b921b020800000000940b68b0

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 1209f652ba516c77e0bdb519d294248ea1be7ac8164d37356194bbaeb42ce465 0.00200000 57 of 58525
01: b8e1783d05539ee7506713f04c51face034c41402a4dc5cd9ffa52491afd470c 10000.00000000 642 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