Tx hash: 50f0e15b916fda9802e2f4f39a05bba020c99808a315a1027b06b10907744f9c

Tx prefix hash: 50f0e15b916fda9802e2f4f39a05bba020c99808a315a1027b06b10907744f9c
Tx public key: 23857691ae11bb43c8624918e15a60c05f954f43e45d10350ac44bf80e26304e
Timestamp: 1517421913 Timestamp [UCT]: 2018-01-31 18:05:13 Age [y:d:h:m:s]: 01:353:12:56:37
Block: 672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 515813 RingCT/type: no
Extra: 0123857691ae11bb43c8624918e15a60c05f954f43e45d10350ac44bf80e26304e02080000000009788b26

2 output(s) for total of 10000.00300000 TUBE

stealth address amount amount idx
00: 2aefb8eda1898ed26e72f84135178b471bf95001883d77d3c1d630ef0a6e2305 0.00300000 63 of 57727
01: e7fb2ad2b7375281e4242243be78aec857fe1fa5638b58399c23ae71246645c2 10000.00000000 708 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