Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 90c385dd849f18f53225223cc3b0973ac4cab83a3983c5e30031378e8f4ce2a0 Tx public key: aa36dd67fe616ceae25f4f59af6a9b704693d64ee5e8317ec5375ae222ddd32b Payment id (encrypted): 561577c91b0eb6a9
Timestamp: 1617913652 Timestamp [UCT]: 2021-04-08 20:27:32 Age [y:d:h:m:s]: 00:005:02:43:22
Block: 673299 Fee (per_kB): 0.40 (0.04) Tx size: 9.9297 kB
Tx version: 2 No of confirmations: 3670 RingCT/type: yes/3
Extra: 01aa36dd67fe616ceae25f4f59af6a9b704693d64ee5e8317ec5375ae222ddd32b020901561577c91b0eb6a9

2 output(s) for total of ? upx

stealth address amount amount idx
00: c460b1e8b1d99e5071db8259738b7b5afb9d6e96968e7a31e3f4e4ef6c11feed ? 3352798 of 3370822
01: 6df80aae1971900885d3dbe69a6103b9d1c73daeddc89607acd078792ba0d6b2 ? 3352799 of 3370822

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