uPlexa Block Explorer

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

Tx hash: 2d2cca2c9a4b5ad7f990c5ce8d61be4cecc45b1b2bd18b0cb45689236c2bf919

Tx prefix hash: 30481219dc5294fca5e2f59a9606188d1fded33e77e9e3b3aca8303464b86e54
Tx public key: 9619d53572e8a928b77af0c0a5b4133d7374e4f52562772dca239b663e6f704e
Timestamp: 1614073850 Timestamp [UCT]: 2021-02-23 09:50:50 Age [y:d:h:m:s]: 00:002:09:18:32
Block: 641309 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 1695 RingCT/type: yes/0
Extra: 019619d53572e8a928b77af0c0a5b4133d7374e4f52562772dca239b663e6f704e02110000004e5f709d00000000000000000000

1 output(s) for total of 1885.55 upx

stealth address amount amount idx
00: a0b76bfc3b2fd9efc16e6d7abbebb38755343e6d1a998f1efe4246bf422f8239 1885.55 3199797 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": 641369, "vin": [ { "gen": { "height": 641309 } } ], "vout": [ { "amount": 188555, "target": { "key": "a0b76bfc3b2fd9efc16e6d7abbebb38755343e6d1a998f1efe4246bf422f8239" } } ], "extra": [ 1, 150, 25, 213, 53, 114, 232, 169, 40, 183, 122, 240, 192, 165, 180, 19, 61, 115, 116, 228, 245, 37, 98, 119, 45, 202, 35, 155, 102, 62, 111, 112, 78, 2, 17, 0, 0, 0, 78, 95, 112, 157, 0, 0, 0, 0, 0, 0, 0, 0, 0, 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