Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: f1ccd37305ce2c5b3af11a5f8a8d122038179ced578309a527c4be534ab39818 Tx public key: 666b3c45fd47ede72b2c7dfcd8f1060d1818054e1e4a86c037a275a901a306c7
Timestamp: 1634175771 Timestamp [UCT]: 2021-10-14 01:42:51 Age [y:d:h:m:s]: 00:009:17:14:32
Block: 808820 Fee (per_kB): 0.08 (0.04) Tx size: 1.8242 kB
Tx version: 2 No of confirmations: 7007 RingCT/type: yes/3
Extra: 01666b3c45fd47ede72b2c7dfcd8f1060d1818054e1e4a86c037a275a901a306c7

2 output(s) for total of ? upx

stealth address amount amount idx
00: 7372f11e89a4e7358aba596cfd7101cdbff5a1c6841edd7df29a9b21dffff6ff ? 3995991 of 4025418
01: fcec77c31b58274dbcd26bb59dc9fd09f505131a43c6cf58f7b4c635a6030a2a ? 3995992 of 4025418

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