Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 7603b4ab6937d80dffd1639a5cc1ab1659d52cc7d1dc5af52a0ba135fefbe481 Tx public key: 7e0cfb18d7e9b9c252f7b9026c4054675f25cca97a1d7fc12e5d5a06e2ce3a3b
Timestamp: 1659813011 Timestamp [UCT]: 2022-08-06 19:10:11 Age [y:d:h:m:s]: 00:011:15:14:24
Block: 1022425 Fee (per_kB): 0.08 (0.04) Tx size: 1.8242 kB
Tx version: 2 No of confirmations: 8371 RingCT/type: yes/3
Extra: 017e0cfb18d7e9b9c252f7b9026c4054675f25cca97a1d7fc12e5d5a06e2ce3a3b

2 output(s) for total of ? upx

stealth address amount amount idx
00: 809d82570d4c5f6a2a30a8af62e2da1d9c82091db92c08e6e10819fee1accd88 ? 4856648 of 4890228
01: df1ca35740c58efe98d961d0485a3baca3c28b6f35157f7c04af96e472294c41 ? 4856649 of 4890228

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