Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 26d2f6e0fc1aded367a83d90921e6804e0f28c299a00e4d64902e53445c8ab4b Tx public key: 21e72f5d027aec787f82dfce40ef0e5474d54cd7e85a77231154eb4be4890c5a Payment id (encrypted): 015732695ee147b7
Timestamp: 1547279935 Timestamp [UCT]: 2019-01-12 07:58:55 Age [y:d:h:m:s]: 04:331:18:46:29
Block: 84702 Fee (per_kB): 7.20 (3.92) Tx size: 1.8379 kB
Tx version: 2 No of confirmations: 1289750 RingCT/type: yes/3
Extra: 020901015732695ee147b70121e72f5d027aec787f82dfce40ef0e5474d54cd7e85a77231154eb4be4890c5a

2 output(s) for total of ? upx

stealth address amount amount idx
00: bfb2e4dafcbefc58fd87c8a0659d14becfceffcf66e2421969de6de9be2d34c9 ? 240459 of 5962526
01: de008eb08651591f30674711f59e9ef4e3f2a029d8208976f4c4a776ad345306 ? 240460 of 5962526

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