uPlexa Block Explorer

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

Tx hash: e7bd04cc6a7145fb17f2390a7b4e12a0bde06eef7da90f8b78a8d98b1efc0f54

Tx prefix hash: 768382a8c4ca2eac0bb753e7dc7a688eb0c23c14a3d3b0b7b2d1013fd610321d
Tx public key: 65f22399cac9459e54286286a34e46b36fc4aa10924f204b20cdbae0e60dddc8
Timestamp: 1614074043 Timestamp [UCT]: 2021-02-23 09:54:03 Age [y:d:h:m:s]: 00:006:05:45:21
Block: 641311 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 4471 RingCT/type: yes/0
Extra: 0165f22399cac9459e54286286a34e46b36fc4aa10924f204b20cdbae0e60dddc8021100000003cab06f00000000010000083300

1 output(s) for total of 1885.47 upx

stealth address amount amount idx
00: 54e9b08adecc3b41ef7cbb6d0c0ce132f8174626e9c97e84ab5c02fa1a3dbea0 1885.47 3199801 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": 641371, "vin": [ { "gen": { "height": 641311 } } ], "vout": [ { "amount": 188547, "target": { "key": "54e9b08adecc3b41ef7cbb6d0c0ce132f8174626e9c97e84ab5c02fa1a3dbea0" } } ], "extra": [ 1, 101, 242, 35, 153, 202, 201, 69, 158, 84, 40, 98, 134, 163, 78, 70, 179, 111, 196, 170, 16, 146, 79, 32, 75, 32, 205, 186, 224, 230, 13, 221, 200, 2, 17, 0, 0, 0, 3, 202, 176, 111, 0, 0, 0, 0, 1, 0, 0, 8, 51, 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