Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 93c7183f39555ee4a0133c7d010be8fbc47cc732bc0d95f7a58d992daa1c8df5 Tx public key: 08fc2b43c722830bbc57f021d6322eee0482c990f059caaa7b6e376c336d3dca Payment id (encrypted): 039ced176bedaab1
Timestamp: 1623361340 Timestamp [UCT]: 2021-06-10 21:42:20 Age [y:d:h:m:s]: 00:008:16:51:06
Block: 718717 Fee (per_kB): 0.44 (0.04) Tx size: 10.7324 kB
Tx version: 2 No of confirmations: 6271 RingCT/type: yes/3
Extra: 0108fc2b43c722830bbc57f021d6322eee0482c990f059caaa7b6e376c336d3dca020901039ced176bedaab1

2 output(s) for total of ? upx

stealth address amount amount idx
00: a2d124184071c21ccbbe58322e64a424787451b6bed44e7b05eecbbee2ec9534 ? 3613503 of 3645903
01: 00cab58d17872b3b28ff2e7545a70179ebef72484aeb922d022e76ae2352b99c ? 3613504 of 3645903

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