uPlexa Block Explorer

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

Tx hash: 6f4669433469965486876cc90df74cb4c564f8524c3138fe4fa29a0adb0ef134

Tx prefix hash: dc409d790a84e1dd9aa4c92d155d38ac0cc5a00bac6fa5d2cb9d3e5b830f9504
Tx public key: 7cb441d1fa2f3ce536941080ac613e0ce3760ec5fc6b82707db0f434ae4d2330
Timestamp: 1593489943 Timestamp [UCT]: 2020-06-30 04:05:43 Age [y:d:h:m:s]: 00:002:04:39:34
Block: 469754 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 1595 RingCT/type: yes/0
Extra: 017cb441d1fa2f3ce536941080ac613e0ce3760ec5fc6b82707db0f434ae4d2330021100000748acf3d500000000000000000000

1 output(s) for total of 1964.19 upx

stealth address amount amount idx
00: 5981b814859953af82e888f60b43cb414cd0e61dbfa76031dd94e7b99e0cfc7d 1964.19 2531969 of 0

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



{ "version": 2, "unlock_time": 469814, "vin": [ { "gen": { "height": 469754 } } ], "vout": [ { "amount": 196419, "target": { "key": "5981b814859953af82e888f60b43cb414cd0e61dbfa76031dd94e7b99e0cfc7d" } } ], "extra": [ 1, 124, 180, 65, 209, 250, 47, 60, 229, 54, 148, 16, 128, 172, 97, 62, 12, 227, 118, 14, 197, 252, 107, 130, 112, 125, 176, 244, 52, 174, 77, 35, 48, 2, 17, 0, 0, 7, 72, 172, 243, 213, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2019-01-05-0432f03 (1.1) | uPlexa version: 0.2.0.2-release