Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: b3ce87d043f2e72f3843230eac661cca29d5ebc99dd866a6a516abb4533cb268 Tx public key: 13a825e0d5a2b2096c580360287b4a6923470f1ca35967a1de4e9c48b85035f4
Timestamp: 1674619093 Timestamp [UCT]: 2023-01-25 03:58:13 Age [y:d:h:m:s]: 00:007:12:56:21
Block: 1145730 Fee (per_kB): 0.08 (0.04) Tx size: 1.8232 kB
Tx version: 2 No of confirmations: 5427 RingCT/type: yes/3
Extra: 0113a825e0d5a2b2096c580360287b4a6923470f1ca35967a1de4e9c48b85035f4

2 output(s) for total of ? upx

stealth address amount amount idx
00: 2bd7f91a9460ac70c8279a979e5cb8fb61d3e8b5ae07b52c1ab455d907b4c66a ? 5267238 of 5284581
01: 43f7a57c3e8b5b4dd99bc27f37a95a7a8489ce9ef89451c72684a7ab546d1d88 ? 5267239 of 5284581

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