Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 11e7a31c7af567cf864b92cbefd5e4df256d0ecc4cbf8d18cdc5d6f33680e3fa Tx public key: fc8a3c73c418bff6e64aa2b197c351e3558684807a781a6bf3fbb3e6e37df580
Timestamp: 1546465209 Timestamp [UCT]: 2019-01-02 21:40:09 Age [y:d:h:m:s]: 04:337:23:47:15
Block: 77892 Fee (per_kB): 2.70 (1.03) Tx size: 2.6328 kB
Tx version: 2 No of confirmations: 1294242 RingCT/type: yes/3
Extra: 01fc8a3c73c418bff6e64aa2b197c351e3558684807a781a6bf3fbb3e6e37df580

2 output(s) for total of ? upx

stealth address amount amount idx
00: 539b6d7ecd6bc9d386821fd953c89243ffef1e369458c158815b80a23b1b449f ? 203884 of 5953779
01: db6f70d7ceb05ae4b16a2a4c25fd6da70302cc9e025b23f1723238a02ace736e ? 203885 of 5953779

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: