Tx hash: d0df4ebf7237e4ac303e8a284802f00188a068e5ca68e679e116a9e61f4ca4b0

Tx prefix hash: 6bfaea4389f2f3f954e7bee071834486cc8f50d6c04bfa31555c5818a2fad9c3
Tx public key: dc950402d51cfbd474b9f46f3a10bccb713a0462c3499545c6dfafe4af371c54
Timestamp: 1533913389 Timestamp [UCT]: 2018-08-10 15:03:09 Age [y:d:h:m:s]: 00:011:05:13:59
Block: 138203 Fee (per_kB): 0.00000000 (0.00000000) Tx size: 0.1982 kB
Tx version: 2 No of confirmations: 8018 RingCT/type: yes/0
Extra: 010837467d033b9078007c2ed5518b0f9b6d2165c66f88f43bfb861eb92e8fe7ac0208000000177854b60001dc950402d51cfbd474b9f46f3a10bccb713a0462c3499545c6dfafe4af371c54

3 output(s) for total of 439.55979725 TUBE

stealth address amount amount idx
00: 6be3e60b795a2fed741e363739c92a398fa2902eefa1ecac9c8b4a17cef19d32 426.37300335 604832 of 0
01: 169be16fe6acb442a4826e261f8dbdd206bdf7c6ed0d8f3620b22e49455ec044 6.59339695 604833 of 0
02: eecda6671e5e2448d4f0a1e065f0a66690a91d555309cb7c77a800225238598d 6.59339695 604834 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