Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 51057e75c04bdb885b1c4a3fde347dabfb580b2f393fe114032542e1d0e66953 Tx public key: 67b45c0767ee4a15cc7e2bf760f288cbda6f8bcd24fccb145de064132297e34c Payment id (encrypted): ab214fa19c835126
Timestamp: 1663966478 Timestamp [UCT]: 2022-09-23 20:54:38 Age [y:d:h:m:s]: 00:012:06:44:45
Block: 1057054 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 8816 RingCT/type: yes/3
Extra: 0167b45c0767ee4a15cc7e2bf760f288cbda6f8bcd24fccb145de064132297e34c020901ab214fa19c835126

2 output(s) for total of ? upx

stealth address amount amount idx
00: ced02e48df98299eb99c3d4f7e9d4381a86ac1a488f10adaac0884bb7e45e2cd ? 4981746 of 5013489
01: e8f46fcea1004117f6f51ca0ad2e036fc7b77c440d1699b4632db56bbf5a4a1c ? 4981747 of 5013489

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