Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 37bb014a0c2858c2413a04ec9ee7f009c6181a253ef7423cc437c8ab4612152f Tx public key: 40e603a96545fafbb047ba5b2aab31ad21ca2b1da5a2575d73fc8c53ba0ab200 Payment id (encrypted): e44de638d6fb1ed1
Timestamp: 1637837932 Timestamp [UCT]: 2021-11-25 10:58:52 Age [y:d:h:m:s]: 00:009:06:16:33
Block: 839366 Fee (per_kB): 0.08 (0.04) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 6669 RingCT/type: yes/3
Extra: 0140e603a96545fafbb047ba5b2aab31ad21ca2b1da5a2575d73fc8c53ba0ab200020901e44de638d6fb1ed1

2 output(s) for total of ? upx

stealth address amount amount idx
00: a9bb20522c1b11cd237a6be937f4781dc69c26ec93cd9bba83acbc199cd6b2b1 ? 4113844 of 4136396
01: b9fde0bc5eaa7cb5dcf271aee6db937c22300cf938a686f67ce1336ce1c535cc ? 4113845 of 4136396

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