Tx hash: 68568a3ec2b41bd37898752409a607831e2a8d3670dd917ee4a3d2825415e416

Tx prefix hash: 68568a3ec2b41bd37898752409a607831e2a8d3670dd917ee4a3d2825415e416
Tx public key: 5de6f549fd95a8ba616c8c90b557331240e2f0ffc61f327ded50e47ed17e2d50
Timestamp: 1517405587 Timestamp [UCT]: 2018-01-31 13:33:07 Age [y:d:h:m:s]: 01:115:08:19:36
Block: 215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 345405 RingCT/type: no
Extra: 015de6f549fd95a8ba616c8c90b557331240e2f0ffc61f327ded50e47ed17e2d50020800000000019e1704

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: f40fd0274c06b97a51a546790d3040c97cd41ca45fc32084b39190123c4b9841 0.00100000 20 of 60493
01: 7e103ec74654bfdbdeebb04274c7d8a9105ce77da284fd0048ab1f884c2a46f4 10000.00000000 224 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