Autorefresh is OFF

Tx hash: 94aa23dbd940090b87ea087d86d88217e670ff0929687a92023ba61585e96259

Tx prefix hash: 94aa23dbd940090b87ea087d86d88217e670ff0929687a92023ba61585e96259
Tx public key: ffb6f909d3c903d909a48efff5eacb9441a933045a99ea49ec97fdc908bc0b31
Timestamp: 1517448751 Timestamp [UCT]: 2018-02-01 01:32:31 Age [y:d:h:m:s]: 05:001:18:03:45
Block: 1169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1304973 RingCT/type: no
Extra: 01ffb6f909d3c903d909a48efff5eacb9441a933045a99ea49ec97fdc908bc0b3102080000000026ab7005

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 085693de1bad4de19696b1d7dfd4ca355b4baebee5bfd0a5cdffe3b6f8523452 0.00200000 569 of 58525
01: ddaf9b45befbe1213271fac9e8035a3c3f92b8bf4b289c69f305e2a09f0bb59a 10000.00000000 1207 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 sent to the server, as the calculations are done on the server 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 sent to the server, as the calculations are done on the server side



{ "version": 1, "unlock_time": 1179, "vin": [ { "gen": { "height": 1169 } } ], "vout": [ { "amount": 200000, "target": { "key": "085693de1bad4de19696b1d7dfd4ca355b4baebee5bfd0a5cdffe3b6f8523452" } }, { "amount": 1000000000000, "target": { "key": "ddaf9b45befbe1213271fac9e8035a3c3f92b8bf4b289c69f305e2a09f0bb59a" } } ], "extra": [ 1, 255, 182, 249, 9, 211, 201, 3, 217, 9, 164, 142, 255, 245, 234, 203, 148, 65, 169, 51, 4, 90, 153, 234, 73, 236, 151, 253, 201, 8, 188, 11, 49, 2, 8, 0, 0, 0, 0, 38, 171, 112, 5 ], "signatures": [ ] }


Less details
source code | explorer version (api): master-2020-03-09-0f3cc6b (1.1) | bittube version: 3.1.0.0-master-34dd77663