Tx hash: 8f6f830f1834fd0793b6b6d60452ae66019c59f47dcf992f7493971561ab680f

Tx prefix hash: 8f6f830f1834fd0793b6b6d60452ae66019c59f47dcf992f7493971561ab680f
Tx public key: f80dd9196ca5f17b0b748f39cb7831a1e7a282ef0e2a76bcb113abdcc03c18db
Timestamp: 1517420676 Timestamp [UCT]: 2018-01-31 17:44:36 Age [y:d:h:m:s]: 02:018:14:23:45
Block: 654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 537390 RingCT/type: no
Extra: 01f80dd9196ca5f17b0b748f39cb7831a1e7a282ef0e2a76bcb113abdcc03c18db020800000000756035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: d4d4bad7fd0eae19fda1f020b8fb75eaa2d9fc842e1ab4c1a4b4ee107cd8b9d7 0.00200000 73 of 58525
01: 3d84fcea4939db8a0b2b456fed38b955c7dbcbc1fe83b7fa6986ae4049cc103f 10000.00000000 689 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: