Tx hash: e09609ac19ff3931f28e1736b512a307840a0b2a661d460bdc50c471f6ccef12

Tx prefix hash: e09609ac19ff3931f28e1736b512a307840a0b2a661d460bdc50c471f6ccef12
Tx public key: 0de5350d26167e54ef5f798a4c05f0d1a12f63386f1f6e3cbf597a54eea7a11d
Timestamp: 1517420834 Timestamp [UCT]: 2018-01-31 17:47:14 Age [y:d:h:m:s]: 01:234:09:03:06
Block: 656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0889 kB
Tx version: 1 No of confirmations: 430400 RingCT/type: no
Extra: 010de5350d26167e54ef5f798a4c05f0d1a12f63386f1f6e3cbf597a54eea7a11d0208000000001ee84694

1 output(s) for total of 10000.00000000 TUBE

stealth address amount amount idx
00: 4af5e8b1223c175ba90f1b52ca57e740aab849aaba5abc96398262112a1773b2 10000.00000000 691 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