Uplexa Block Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Transaction

Autorefresh is OFF
Tx hash: c3e2a188621bc93f8bb63c14e18bec4f60cc4cbe85eb6fb6ed9ba815aa1c0fba Tx public key: 3a20f0ecc7ee354454aecd04edc994b96f4a11dee8e1091bbebb6f12c5713cfa Payment id (encrypted): 91160f9eed7168c3
Timestamp: 1546460195 Timestamp [UCT]: 2019-01-02 20:16:35 Age [y:d:h:m:s]: 04:338:02:17:47
Block: 77859 Fee (per_kB): 7.20 (3.92) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 1294310 RingCT/type: yes/3
Extra: 02090191160f9eed7168c3013a20f0ecc7ee354454aecd04edc994b96f4a11dee8e1091bbebb6f12c5713cfa

2 output(s) for total of ? upx

stealth address amount amount idx
00: 02815a1fb39907161bba125ab7125ae3f051998246860d8bb962b3086524056b ? 203611 of 5953911
01: d513875942ca2d2c980b4fe8d1255cbaa88e29c550dee1644d0213f102627201 ? 203612 of 5953911

Check which outputs belong to given uPlexa 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 uPlexa in this transaction

Tx private key can be obtained using get_tx_key command in uplexa-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




source code | explorer version (api): master-2019-01-05-0432f03 (1.1) | uPlexa version: 0.2.2.0-45887ac92