Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: dbd3a13a12a8c0ae9f0077c9a87b25e95a6ee2c81558f6530255d1b39996777c Tx public key: 5e7c2857e77f1b2c012b79d8a3ae689d850f95fcde6db7dddbe10cb9463f903b
Timestamp: 1626930248 Timestamp [UCT]: 2021-07-22 05:04:08 Age [y:d:h:m:s]: 00:010:21:32:21
Block: 748487 Fee (per_kB): 0.56 (0.04) Tx size: 13.1641 kB
Tx version: 2 No of confirmations: 7835 RingCT/type: yes/3
Extra: 015e7c2857e77f1b2c012b79d8a3ae689d850f95fcde6db7dddbe10cb9463f903b

2 output(s) for total of ? upx

stealth address amount amount idx
00: 4cf379212070d2f1b284108347977f74f882aa45bda9876d3f224da1265d0e1f ? 3760807 of 3794163
01: 4c0cdb4ef2bf34b357bdccdbc84a5c5cacb04e8fd3cdfb04dd720287043f20e6 ? 3760808 of 3794163

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