Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: e4204fd73dc80e30dfc79f2b7910a4fe7bc16ea23d9eb57264154d7b0d54fad0 Tx public key: 41385e0a4079a50cc621e2e47ddb0e6b94833b3d4d3a89da0261abee0bd0813d Payment id (encrypted): 51a8918884b6a94b
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:14:04:43
Block: 691750 Fee (per_kB): 1.26 (0.10) Tx size: 13.1982 kB
Tx version: 2 No of confirmations: 4754 RingCT/type: yes/3
Extra: 0141385e0a4079a50cc621e2e47ddb0e6b94833b3d4d3a89da0261abee0bd0813d02090151a8918884b6a94b

2 output(s) for total of ? upx

stealth address amount amount idx
00: 37f19af08d794199a0b38bdfe74fd6ac8fb59eb3db356940a348729796ed154f ? 3461186 of 3489644
01: f2b8a44a6af9fde4bd632b2e3534147a06a2c4588cef74f5b0ac3dbb47cd9eae ? 3461187 of 3489644

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: