uPlexa Block Explorer

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

Tx hash: 6a3d4af05860fe167ff4a24258ffc8e179bf5fa59e1dbd0e3a2e40492c07e73a

Tx prefix hash: 43a329c65452398b1497cfa51686475cc4aea7cc605a6f7828e333bf38138e3c
Tx public key: 8d0cc3f50c2f912b7e49c44cca5d715ed37c6d65692283e7a4fb3f3469ccad7e
Timestamp: 1565728567 Timestamp [UCT]: 2019-08-13 20:36:07 Age [y:d:h:m:s]: 00:012:07:19:49
Block: 238585 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 8879 RingCT/type: yes/0
Extra: 018d0cc3f50c2f912b7e49c44cca5d715ed37c6d65692283e7a4fb3f3469ccad7e021116b4305600000000000000000000000000

1 output(s) for total of 4214.44 upx

stealth address amount amount idx
00: 4843c52cdf16ecabc006d2360a1db6bfab81c8222ee6d83d379f54fc04605d53 4214.44 1354263 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": 238645, "vin": [ { "gen": { "height": 238585 } } ], "vout": [ { "amount": 421444, "target": { "key": "4843c52cdf16ecabc006d2360a1db6bfab81c8222ee6d83d379f54fc04605d53" } } ], "extra": [ 1, 141, 12, 195, 245, 12, 47, 145, 43, 126, 73, 196, 76, 202, 93, 113, 94, 211, 124, 109, 101, 105, 34, 131, 231, 164, 251, 63, 52, 105, 204, 173, 126, 2, 17, 22, 180, 48, 86, 0, 0, 0, 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