Tx hash: 6061c5818714634d31df1eb4907098232bf262ed597dd74287fb1688a10c9f05

Tx prefix hash: 6061c5818714634d31df1eb4907098232bf262ed597dd74287fb1688a10c9f05
Tx public key: a1a774158f8e57223bb7c5dae80d9c46d64dc8cd50728e9159096caef68ea3ca
Timestamp: 1517427767 Timestamp [UCT]: 2018-01-31 19:42:47 Age [y:d:h:m:s]: 01:146:16:18:54
Block: 802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 367434 RingCT/type: no
Extra: 01a1a774158f8e57223bb7c5dae80d9c46d64dc8cd50728e9159096caef68ea3ca020800000000350b68b0

2 output(s) for total of 10000.02000000 TUBE

stealth address amount amount idx
00: f02c2aff78ca4e9b65ca9a55f5defbd1386a1fc4eb20bfe0d3a56959046aa747 0.02000000 175 of 151559
01: 3da16fd29fbdcac7f0f2ae2828fa6b1e9cbb2e7cb38cfdead3bf33ae0992ab91 10000.00000000 840 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