Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 696741f41a34f2e103f35266e130bb25ff22d9de67ce96143e23f35c677f17a5 Tx public key: 7bd89cd9e11de64dbae136ff863421045a3b10f0619384b30f8b85f0808e8e10 Payment id (encrypted): 39db4ea5d9f566a3
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:13:22:42
Block: 691750 Fee (per_kB): 0.32 (0.17) Tx size: 1.8398 kB
Tx version: 2 No of confirmations: 4730 RingCT/type: yes/3
Extra: 017bd89cd9e11de64dbae136ff863421045a3b10f0619384b30f8b85f0808e8e1002090139db4ea5d9f566a3

2 output(s) for total of ? upx

stealth address amount amount idx
00: fea3fb203c8d5ea2e60ffde25dddba67de14aa904dac9e57a193244285564247 ? 3461168 of 3489509
01: 95a2bb1d088935b80a43c423ed8b64564d6c4e6a309c116f3585c7048a5e6cb9 ? 3461169 of 3489509

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