uPlexa Block Explorer

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

Tx hash: 57f08cba7a94ac9a5c292f3c0f37a2a60a7a2577648cdeea282aa76a5ef1d74d

Tx prefix hash: 106695a0caf1f459163201d6624881f9366cad01584aafbd11b14db9b54608d0
Tx public key: d5372bcfc0412465c507a698c002c19057ecc8cbb299cfd379c0ea0005e881cb
Timestamp: 1593490001 Timestamp [UCT]: 2020-06-30 04:06:41 Age [y:d:h:m:s]: 00:002:05:11:36
Block: 469755 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 1607 RingCT/type: yes/0
Extra: 01d5372bcfc0412465c507a698c002c19057ecc8cbb299cfd379c0ea0005e881cb02110000001392da4500000000000000000000

1 output(s) for total of 1964.19 upx

stealth address amount amount idx
00: 3d8d2e31fa83a7f7cdd835d06f9c160d1bef461d52a83b27c0a45dd8fb59db12 1964.19 2531970 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": 469815, "vin": [ { "gen": { "height": 469755 } } ], "vout": [ { "amount": 196419, "target": { "key": "3d8d2e31fa83a7f7cdd835d06f9c160d1bef461d52a83b27c0a45dd8fb59db12" } } ], "extra": [ 1, 213, 55, 43, 207, 192, 65, 36, 101, 197, 7, 166, 152, 192, 2, 193, 144, 87, 236, 200, 203, 178, 153, 207, 211, 121, 192, 234, 0, 5, 232, 129, 203, 2, 17, 0, 0, 0, 19, 146, 218, 69, 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