Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: e928b94fddd2394a88944996b65a0b0802c555d48e29703bc7fe45d35bad47e4 Tx public key: 3d61e9324bca2c92222daeffb3f7bc7eb543ab67834a618bd80fcf113814cdfc Payment id (encrypted): f1d54af1e2219ba6
Timestamp: 1620125439 Timestamp [UCT]: 2021-05-04 10:50:39 Age [y:d:h:m:s]: 00:006:14:30:48
Block: 691755 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 4765 RingCT/type: yes/3
Extra: 013d61e9324bca2c92222daeffb3f7bc7eb543ab67834a618bd80fcf113814cdfc020901f1d54af1e2219ba6

2 output(s) for total of ? upx

stealth address amount amount idx
00: a3ffef93cab7e824f32cebde88b2e77ae86a4d83f0425d1474a0d40289be70ae ? 3461226 of 3489727
01: 1c0ca09ef9050e39f670a3c77ac006101472534778b22291144e61269a516929 ? 3461227 of 3489727

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: