Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 13cb9e98bddc76446bdf377da4db36ce45864f63299f779c2c036be4d04f53c7 Tx public key: d8821396cba4efba338a45e7b46b552048713d2d138cef2ad94f46a49fa6a701 Payment id (encrypted): 4b14c441a5c070eb
Timestamp: 1547279935 Timestamp [UCT]: 2019-01-12 07:58:55 Age [y:d:h:m:s]: 04:331:17:43:51
Block: 84702 Fee (per_kB): 10.80 (4.09) Tx size: 2.6416 kB
Tx version: 2 No of confirmations: 1289708 RingCT/type: yes/3
Extra: 0209014b14c441a5c070eb01d8821396cba4efba338a45e7b46b552048713d2d138cef2ad94f46a49fa6a701

2 output(s) for total of ? upx

stealth address amount amount idx
00: d4011e961c1a5103537cfc5c78cfa27d0d3809dc334dac8b53d15159802c7107 ? 240451 of 5962373
01: b09aafe6a73f23dfbf331a88b9782f56a7c62b4fc5bb2411c515d0f103f3ca54 ? 240452 of 5962373

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: