Tx hash: 9369e9163274f52d867418f078058e804e40cd14efabfc6b8df8cf9a1397edb9

Tx prefix hash: 9369e9163274f52d867418f078058e804e40cd14efabfc6b8df8cf9a1397edb9
Tx public key: 8d09cc6bc90c164c94aa6259c80838ca452c22d50047ff8f356e7bea41362308
Timestamp: 1517405728 Timestamp [UCT]: 2018-01-31 13:35:28 Age [y:d:h:m:s]: 01:115:08:52:21
Block: 220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 345413 RingCT/type: no
Extra: 018d09cc6bc90c164c94aa6259c80838ca452c22d50047ff8f356e7bea41362308020800000000010b68b0

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 761af3f170f03ef08ea311bda8d63fbd3f1019f3bea642b1be240c3debcb0c22 0.00100000 22 of 60493
01: de672f7266d7f4e051b5f12cbddf78a26e22986178259977f841e646a96254a7 10000.00000000 230 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-01-31-3693d4a (1.1) | BitTube version: 2.1.0.0-master-release