Tx hash: 8b2e0da7cf164bcbd4e4f57462f93f9f7c30083906a1c5e45d132aa4a8d5e605

Tx prefix hash: 8b2e0da7cf164bcbd4e4f57462f93f9f7c30083906a1c5e45d132aa4a8d5e605
Tx public key: 70d9b64579964d5ca3edea50e172c5e001516ac706c60d1fca47f22ae5c665ee
Timestamp: 1517422549 Timestamp [UCT]: 2018-01-31 18:15:49 Age [y:d:h:m:s]: 01:318:06:39:52
Block: 683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 490543 RingCT/type: no
Extra: 0170d9b64579964d5ca3edea50e172c5e001516ac706c60d1fca47f22ae5c665ee0208000000005c0b68b0

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: fb205c704c70dad9e0580b41a03cbe77134bd9616217e8a7b46f2d34da261f39 0.00100000 205 of 60494
01: 14a394b8c3f0afac14a4a5de3ba577458f948b6d0a0ee8afa435ab236ed7fefe 10000.00000000 719 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: 2.1.0.1-master-release