uPlexa Block Explorer

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

Tx hash: 13a5347d4714c1183f3618e67dbc5918ca2eb6d1fc2bd384dd7e63a23db32a4d

Tx prefix hash: 542c34ae2d8f60a080526bfd121ba3e5cb78ef52d458137688bbb6f50583dc85
Tx public key: 0a5ba1381a1375c46ec0878bfc98629df0f6815aaaaeec7e850a3a10239707b8
Timestamp: 1614073745 Timestamp [UCT]: 2021-02-23 09:49:05 Age [y:d:h:m:s]: 00:006:07:29:18
Block: 641308 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 4518 RingCT/type: yes/0
Extra: 010a5ba1381a1375c46ec0878bfc98629df0f6815aaaaeec7e850a3a10239707b80211000000072d3a2c0000000001000002be00

1 output(s) for total of 1885.47 upx

stealth address amount amount idx
00: 9d7efa9a838168640e2eadd8de71fb7b3fe84d360f9b3af86146bfbca4144cb2 1885.47 3199796 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": 641368, "vin": [ { "gen": { "height": 641308 } } ], "vout": [ { "amount": 188547, "target": { "key": "9d7efa9a838168640e2eadd8de71fb7b3fe84d360f9b3af86146bfbca4144cb2" } } ], "extra": [ 1, 10, 91, 161, 56, 26, 19, 117, 196, 110, 192, 135, 139, 252, 152, 98, 157, 240, 246, 129, 90, 170, 174, 236, 126, 133, 10, 58, 16, 35, 151, 7, 184, 2, 17, 0, 0, 0, 7, 45, 58, 44, 0, 0, 0, 0, 1, 0, 0, 2, 190, 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