Tx hash: 5a52abd5cbb63f8dfec4dae81bd071e5741ed6f572d3a42e8b08e2fce544e684

Tx prefix hash: 5a52abd5cbb63f8dfec4dae81bd071e5741ed6f572d3a42e8b08e2fce544e684
Tx public key: fa42e14b5cc3063a5ff8ec9d45c755cbabea9aab5a950b3fc0d99ce6d84e9eb8
Timestamp: 1517405769 Timestamp [UCT]: 2018-01-31 13:36:09 Age [y:d:h:m:s]: 01:110:16:56:26
Block: 223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0889 kB
Tx version: 1 No of confirmations: 342079 RingCT/type: no
Extra: 01fa42e14b5cc3063a5ff8ec9d45c755cbabea9aab5a950b3fc0d99ce6d84e9eb802080000000004edfc57

1 output(s) for total of 10000.00000000 TUBE

stealth address amount amount idx
00: 3d6c8dd0069521718b441e01e7484f72d8df5982df7db57545fc065ee88ffeb7 10000.00000000 233 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