Autorefresh is ON (10 s)

Tx hash: f28efa0607a28c4ebda4531372d3ff403e3104e192a09598ad4cd1e5cffb999b

Tx prefix hash: f28efa0607a28c4ebda4531372d3ff403e3104e192a09598ad4cd1e5cffb999b
Tx public key: 3dfa9b6b4c51b433caaa8256b7186608873e32d64106918af8040312ffb88d82
Timestamp: 1517413876 Timestamp [UCT]: 2018-01-31 15:51:16 Age [y:d:h:m:s]: 02:356:06:11:37
Block: 490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 779742 RingCT/type: no
Extra: 013dfa9b6b4c51b433caaa8256b7186608873e32d64106918af8040312ffb88d82020800000000150b68b0

2 output(s) for total of 10000.00300000 TUBE

stealth address amount amount idx
00: a1617c9785d622ac179195bc4b4260d4748a82a1872dae0f20f4b36787d9128e 0.00300000 13 of 57727
01: 800517c0a43f71fa175734671c65e7580c19b8b93ae2bd96e9b9cae7553bd5a9 10000.00000000 515 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 sent to the server, as the calculations are done on the server 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 sent to the server, as the calculations are done on the server side

More details
source code | explorer version (api): master-2020-03-09-0f3cc6b (1.1) | bittube version: