Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 42a7ec55db1d329a8311d728c5eae2271143d1fdd64e698a83b236612a28ee29 Tx public key: 46fbf1c59fbd9840b8821510b61de454c4c77ced70eb9f0da9dd969453466cce Payment id (encrypted): 970b6f99d7599274
Timestamp: 1634175465 Timestamp [UCT]: 2021-10-14 01:37:45 Age [y:d:h:m:s]: 00:009:14:46:59
Block: 808817 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 6933 RingCT/type: yes/3
Extra: 0146fbf1c59fbd9840b8821510b61de454c4c77ced70eb9f0da9dd969453466cce020901970b6f99d7599274

2 output(s) for total of ? upx

stealth address amount amount idx
00: 7e6b6342180bf929779716fc39900f124220ee7f828a73498991c8c9edb3cdde ? 3995976 of 4025160
01: 2d611fba0f3452c865702ef1650d3f67c93c902efe8db2a61224279174ca083e ? 3995977 of 4025160

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