Autorefresh is ON (10 s)

Tx hash: b118db3d8e6c6ae438128bcc9aa4f56c6816da62fecb8740ca8c049d31e14f89

Tx prefix hash: b118db3d8e6c6ae438128bcc9aa4f56c6816da62fecb8740ca8c049d31e14f89
Tx public key: 768b00b654a434562090fb3470338665dd1866673a7c8d8efecfa7b22468c91c
Timestamp: 1517407455 Timestamp [UCT]: 2018-01-31 14:04:15 Age [y:d:h:m:s]: 03:027:19:33:57
Block: 292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 806104 RingCT/type: no
Extra: 01768b00b654a434562090fb3470338665dd1866673a7c8d8efecfa7b22468c91c020800000000410b68b0

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: d46090bb12773c07bd6d64ba6708a464878fd19de208f58859da5f5f1b87c158 0.00100000 46 of 60494
01: a0a7aa7b6f0218af5b6b63b2ed0c97e690577c42b466de655d1cd33c22c9e37f 10000.00000000 307 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: