Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: f109f07a2cc3bc73d5ec36a624d6aae32dc72f3b6d0322b522d352aa4c42af9e Tx public key: 672bb559fddd5c62e6af72aeefcbaa8e5e9bf9cd9ee05d30925d4b5943f31fb8
Timestamp: 1617856375 Timestamp [UCT]: 2021-04-08 04:32:55 Age [y:d:h:m:s]: 00:005:17:45:30
Block: 672815 Fee (per_kB): 0.12 (0.05) Tx size: 2.6348 kB
Tx version: 2 No of confirmations: 4134 RingCT/type: yes/3
Extra: 01672bb559fddd5c62e6af72aeefcbaa8e5e9bf9cd9ee05d30925d4b5943f31fb8

2 output(s) for total of ? upx

stealth address amount amount idx
00: 2189dd535731eb9ae799150761c8c91f9f856b0e0251b1b3a4f6022b795986b3 ? 3341795 of 3370705
01: d095e6367de1c685d85a3547d0c673f704cc5f18b4ea1b11659b11ffdf9a907b ? 3341796 of 3370705

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: