Tx hash: 5e7b70e002b385338ebc62d4c4589d0267c93ac62e08dda35f5dd4474db5c8ac

Tx prefix hash: 5e7b70e002b385338ebc62d4c4589d0267c93ac62e08dda35f5dd4474db5c8ac
Tx public key: a5d37633063de7f644701edca55f6eada931b781d26052b1b5532a28ca8df691
Timestamp: 1517420722 Timestamp [UCT]: 2018-01-31 17:45:22 Age [y:d:h:m:s]: 02:025:20:50:40
Block: 655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 542606 RingCT/type: no
Extra: 01a5d37633063de7f644701edca55f6eada931b781d26052b1b5532a28ca8df691020800000000956035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 86dbcd8558e2a5fba8561b1616ccc15429b11b7135688bae4f0d403065058c24 0.00200000 74 of 58525
01: 3a11ab508b43e5892b2f93d889e92cd96a893cce591720351f7f00501c02fb99 10000.00000000 690 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: