Tx hash: ad3fe2fef37ac7b2a604c0cb903a460e22eb206e0aaac171248a5a7695bedec0

Tx prefix hash: ad3fe2fef37ac7b2a604c0cb903a460e22eb206e0aaac171248a5a7695bedec0
Tx public key: 3f0d5e9e8ab79b56f63dd7170de6c52bd1451a6d4b8fcb36d24daf2052d41518
Timestamp: 1517462152 Timestamp [UCT]: 2018-02-01 05:15:52 Age [y:d:h:m:s]: 01:317:01:56:15
Block: 1327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 489369 RingCT/type: no
Extra: 013f0d5e9e8ab79b56f63dd7170de6c52bd1451a6d4b8fcb36d24daf2052d41518020800000000a16035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: ea50e85ccd3c9a7366552706ea17b018396a2914890b7e934e4b96eec4c0d379 0.00200000 726 of 58525
01: 04985b03a9faaa79bac3f5be0182d604bfc2035286513fff47f11ff165d6dbf8 10000.00000000 1365 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