Tx hash: eb6bd2c44121f08df6bf39276ccd76c1aabd978856bed140e9ea3c2021251082

Tx prefix hash: eb6bd2c44121f08df6bf39276ccd76c1aabd978856bed140e9ea3c2021251082
Tx public key: 0eefe781b4b6ad9a34958de0bf2e28eaabb504f88e2dfd6802531916206525f8
Timestamp: 1517419008 Timestamp [UCT]: 2018-01-31 17:16:48 Age [y:d:h:m:s]: 01:286:00:22:59
Block: 613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 467447 RingCT/type: no
Extra: 010eefe781b4b6ad9a34958de0bf2e28eaabb504f88e2dfd6802531916206525f8020800000027056035b3

2 output(s) for total of 10000.00300000 TUBE

stealth address amount amount idx
00: 8ac601ff213cfd71802d9da02cefeb2131ec20f8b47d9ee4cdb1ad5c2c6db728 0.00300000 51 of 57727
01: 7b3aac8157484ec96611004c0e8c3be55f25d607b64f796bd97acb35bc86fda5 10000.00000000 646 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: