Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: dd72c9c2d5e3d2f0c3bc1cd4514c8dee1401f7d056cf026cc41d588aee347a89 Tx public key: 3c6a3c023a8d00910a271aa4cef5e0e1f7fefb64f2aaa2a3bef730c3e54623e4
Timestamp: 1548144845 Timestamp [UCT]: 2019-01-22 08:14:05 Age [y:d:h:m:s]: 04:321:17:37:19
Block: 91900 Fee (per_kB): 1.80 (0.99) Tx size: 1.8262 kB
Tx version: 2 No of confirmations: 1282520 RingCT/type: yes/3
Extra: 013c6a3c023a8d00910a271aa4cef5e0e1f7fefb64f2aaa2a3bef730c3e54623e4

2 output(s) for total of ? upx

stealth address amount amount idx
00: 162a599d05a9071477d3d3e02b295ec58801d3dc89aace4d438ec94132cc56b7 ? 277150 of 5962411
01: dd919da963937834863f649c4ad3bd2e8ac41e07db5d088cd43ae8fe664c1315 ? 277151 of 5962411

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: