Tx hash: bf502e0ce3d958c0db6bf76ea8d8c1aaacc5cb242c06c8eb674de2583c7f2140

Tx prefix hash: bf502e0ce3d958c0db6bf76ea8d8c1aaacc5cb242c06c8eb674de2583c7f2140
Tx public key: 71af244615b01e3a85a09ca3bc8f5bf64931e53d33603e675f9dd7ab5e6f089d
Timestamp: 1517422730 Timestamp [UCT]: 2018-01-31 18:18:50 Age [y:d:h:m:s]: 01:315:11:51:48
Block: 690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 488532 RingCT/type: no
Extra: 0171af244615b01e3a85a09ca3bc8f5bf64931e53d33603e675f9dd7ab5e6f089d02080000000005c4f184

2 output(s) for total of 10000.00300000 TUBE

stealth address amount amount idx
00: bfcaecf04c342873b829a67cdfab31d192b233c1044f7d5af5141a61a0f9a227 0.00300000 70 of 57727
01: 041317355fa124818001c43ac3fdeefe007f510dfb147f2b61f026a350f3805a 10000.00000000 726 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