Tx hash: d67d3047aef16aae02a6b461f61010175183b87acc678a31d6c1e0d3fb0e9d1a

Tx prefix hash: d67d3047aef16aae02a6b461f61010175183b87acc678a31d6c1e0d3fb0e9d1a
Tx public key: 386e2aff244771fc538ed7f6d357b1a454a87e23d3bce2dceabdf2868087d46b
Timestamp: 1517427617 Timestamp [UCT]: 2018-01-31 19:40:17 Age [y:d:h:m:s]: 01:232:18:11:49
Block: 800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0889 kB
Tx version: 1 No of confirmations: 429163 RingCT/type: no
Extra: 01386e2aff244771fc538ed7f6d357b1a454a87e23d3bce2dceabdf2868087d46b02080000000029ab7005

1 output(s) for total of 10000.00000000 TUBE

stealth address amount amount idx
00: ef6bcbad25cb9da7a8ef768e989979fce42c20613772ca3a24dc18734bb15fae 10000.00000000 838 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