Tx hash: 66c0adc74567703dfda5ba521cf55980375133fcbbbc361cd0fb61107b706df0

Tx prefix hash: 66c0adc74567703dfda5ba521cf55980375133fcbbbc361cd0fb61107b706df0
Tx public key: e646d46076bb107d744415c199f83164db914df71c986ac72199f14e6011a916
Timestamp: 1517412108 Timestamp [UCT]: 2018-01-31 15:21:48 Age [y:d:h:m:s]: 02:023:23:35:15
Block: 444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 541392 RingCT/type: no
Extra: 01e646d46076bb107d744415c199f83164db914df71c986ac72199f14e6011a916020800000000019e1704

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 19435666ce7c724f87897eb1d4fa24541c78cf91facf8c7db1e23b12d8fe81e9 0.00100000 95 of 60494
01: 02bd2007ba6804a8bfb43a847656d1320ac18b376d8fef5cc1c53bbf842e8daa 10000.00000000 463 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