Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 4381595b35f6b6163ed94dcc7b5a8cb971f34ca05e8227f02610a0c159bd2816 Tx public key: 96d0082bc396bbaa8a97526f6749fbaa72b282ac7afe086fc8a67fe779b93663 Payment id (encrypted): a650ef7a20657948
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:14:46:41
Block: 691750 Fee (per_kB): 0.08 (0.04) Tx size: 1.8389 kB
Tx version: 2 No of confirmations: 4777 RingCT/type: yes/3
Extra: 0196d0082bc396bbaa8a97526f6749fbaa72b282ac7afe086fc8a67fe779b93663020901a650ef7a20657948

2 output(s) for total of ? upx

stealth address amount amount idx
00: a1673d66de5c37e3a90f01b0114a8cbef76fbca7d86a102e8a04be7734587659 ? 3461200 of 3489767
01: 537207298780f6ce2d2ffacc303f1293845fa2e677685e297ee0ff520cf7cf26 ? 3461201 of 3489767

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: