Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: cc8a1ce05a6aafbb0a149aeaea8054780b093d7aba60117f84da06cb04b67164 Tx public key: 172e64cfd193aedc62161b1a15f89f7a747041e3d13f43aa50ddfcb137514436 Payment id (encrypted): 56eb3c3a4200f202
Timestamp: 1695323430 Timestamp [UCT]: 2023-09-21 19:10:30 Age [y:d:h:m:s]: 00:078:06:56:05
Block: 1318096 Fee (per_kB): 0.12 (0.05) Tx size: 2.6396 kB
Tx version: 2 No of confirmations: 56331 RingCT/type: yes/3
Extra: 01172e64cfd193aedc62161b1a15f89f7a747041e3d13f43aa50ddfcb13751443602090156eb3c3a4200f202

2 output(s) for total of ? upx

stealth address amount amount idx
00: 0bc5638a423ea774f24b47500fe9cc68778a8bf044d7889c7cbd0ebfa6946cbc ? 5773484 of 5962428
01: 87d0f6cb971ce294465728d61d54e80362c7f50fe839b04cd630a1d7c379605c ? 5773485 of 5962428

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