Tx hash: d2f44aeff20a91061d4bb72b0b5144a84e29d2946a8b07441023965c506eb87c

Tx prefix hash: d2f44aeff20a91061d4bb72b0b5144a84e29d2946a8b07441023965c506eb87c
Tx public key: 787fa698a13249c28c729f4b9fa886e5d0df1b7e29f9049d7664ba5551b875c3
Timestamp: 1517405738 Timestamp [UCT]: 2018-01-31 13:35:38 Age [y:d:h:m:s]: 01:050:02:30:56
Block: 221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0889 kB
Tx version: 1 No of confirmations: 298606 RingCT/type: no
Extra: 01787fa698a13249c28c729f4b9fa886e5d0df1b7e29f9049d7664ba5551b875c3020800000000010b68b0

1 output(s) for total of 10000.00000000 TUBE

stealth address amount amount idx
00: de6604e16c57d90cc8194324d1aaa0248a9a79492b3472c6dff7298fcc7d7f6c 10000.00000000 231 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-01-31-3693d4a (1.1) | BitTube version: 2.1.0.0-master-release