Tx hash: abcd16ca1e9297a13ab6766b702d5f24f2598aeaa3e5ac6e6eb87348cde889b4

Tx prefix hash: abcd16ca1e9297a13ab6766b702d5f24f2598aeaa3e5ac6e6eb87348cde889b4
Tx public key: 12f84b25844827c3e7452d5c805373b3ce970c68a32499a8f4a0fddb138c949e
Timestamp: 1517420509 Timestamp [UCT]: 2018-01-31 17:41:49 Age [y:d:h:m:s]: 02:018:13:09:35
Block: 648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 537370 RingCT/type: no
Extra: 0112f84b25844827c3e7452d5c805373b3ce970c68a32499a8f4a0fddb138c949e02080000000030e971d2

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 2bc8cdbed083aea23e5f37167b96bec5f0b6a4017dc5e6c3f9bc445dd4919f5b 0.00100000 190 of 60494
01: 8abc7cdd9bdd5aa1bac6fd150a8850e697135c4cf6a0b8c6ec8b7cd7c6100866 10000.00000000 683 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: