Tx hash: b451671d2945973e68564f0a2842411cbac52f2faf2a6929261fb08c972bf189

Tx prefix hash: b451671d2945973e68564f0a2842411cbac52f2faf2a6929261fb08c972bf189
Tx public key: 3557c808afd4c19f66a1d2e67345d117243b22814952525f123da403c38f9c76
Timestamp: 1517417020 Timestamp [UCT]: 2018-01-31 16:43:40 Age [y:d:h:m:s]: 02:063:19:29:28
Block: 566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 569882 RingCT/type: no
Extra: 013557c808afd4c19f66a1d2e67345d117243b22814952525f123da403c38f9c76020800000014046035b3

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: fa3bf6c557d72b1cc3e009cfc45f66e0ee006d5809175c856b88612af1637762 0.00100000 145 of 60494
01: c0c99c3b734686a3b7cd1f9799ddc317df0e6b831ecacd7f3ea2bd0e7f638873 10000.00000000 598 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