Tx hash: 872a3cbb251d0b33b32b397184e2d3a925fccec5b79c5d3d32e4cf70965fa601

Tx prefix hash: 65a253ea0f6b3022534879834a9c07253ce45f816e84163dba312cd967d94406
Tx public key: 53e05ed264815d9aa90d744c6bc52f06c0781ee5213e4d6b366943fc2e0c9c1e
Timestamp: 1533909326 Timestamp [UCT]: 2018-08-10 13:55:26 Age [y:d:h:m:s]: 00:127:16:41:32
Block: 138159 Fee (per_kB): 0.00000000 (0.00000000) Tx size: 0.2070 kB
Tx version: 2 No of confirmations: 91565 RingCT/type: yes/0
Extra: 0195611f43bcf108b96b86e1706c1405940c754f6a410d186b63faea792fa0e67e0211d00a7dc8558bf2930000000000000000000153e05ed264815d9aa90d744c6bc52f06c0781ee5213e4d6b366943fc2e0c9c1e

3 output(s) for total of 439.86597296 TUBE

stealth address amount amount idx
00: 93c0eac7e599e01c31dfdbaa27c99b93541e64bd0b107b31b38d99cbbfd1d078 426.66999378 604008 of 0
01: cfe5335f66824353a3a895cad45a971eb867808fc64b0812a797b78855121170 6.59798959 604009 of 0
02: f5b1660cd52665686a7bfd8f7422b7561a30808fe68f7a30b3846a97ae76e494 6.59798959 604010 of 0

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-2018-08-13-8510232 (1.1) | BitTube version: 2.0.0.3-master-ce967c29