Tx hash: c7da5188181ec8cfe6209b041642e0b7aacc0f60a9fd4124ec0d8066cf365323

Tx prefix hash: 0ba09958f27fd42100c07a8157abddecf52916e70cc12000acc55a7a6964af00
Tx public key: 0b5ce0cb0e85571184e9d665dc589760842e4ba91ce606eded65e1b25c258eb7
Timestamp: 1532659858 Timestamp [UCT]: 2018-07-27 02:50:58 Age [y:d:h:m:s]: 01:079:15:24:50
Block: 127796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1982 kB
Tx version: 2 No of confirmations: 318766 RingCT/type: yes/0
Extra: 01da7c58f729053c35dc65d13be4c6dba4ccc12eec907e6847b333ec1bf8e3bca9020800000114c51b1000010b5ce0cb0e85571184e9d665dc589760842e4ba91ce606eded65e1b25c258eb7

3 output(s) for total of 441.74650959 TUBE

stealth address amount amount idx
00: 16fad01562776628f94abfaf4d122af3905ac5db1bcd9e84a66a0ca50c347d4b 428.49411431 393890 of 0
01: 45426dc1164faf8d8dc4deea3bc3c0b0a104e2979f55b2fc8849784000e32fb7 6.62619764 393891 of 0
02: 8a53a689004675faef94623f1459657a0f0abcaa489323cda7f7fd198ce6c0f2 6.62619764 393892 of 0

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