uPlexa Block Explorer

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

Tx hash: 4a0315c1c6e301ad12efc353cab2b683f66d9a42b03930c473c13267108d9bb4

Tx prefix hash: 22f98ce2fd0be24ba6de32aab3fdb7f545f97f1db3fd67ba80ea803545f27ec2
Tx public key: a260bfa4c14ef5ac136f04d76279546bf9357e5d7fc9c7211d18470f0545d998
Timestamp: 1614073889 Timestamp [UCT]: 2021-02-23 09:51:29 Age [y:d:h:m:s]: 00:006:06:41:55
Block: 641310 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 4493 RingCT/type: yes/0
Extra: 01a260bfa4c14ef5ac136f04d76279546bf9357e5d7fc9c7211d18470f0545d998021100000004cab06f000000000100000a1700

1 output(s) for total of 1885.47 upx

stealth address amount amount idx
00: 382dc21cb8184110a99dc7f07d9ad2c6f51f533a5194bb422387ab261e7d370b 1885.47 3199800 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": 641370, "vin": [ { "gen": { "height": 641310 } } ], "vout": [ { "amount": 188547, "target": { "key": "382dc21cb8184110a99dc7f07d9ad2c6f51f533a5194bb422387ab261e7d370b" } } ], "extra": [ 1, 162, 96, 191, 164, 193, 78, 245, 172, 19, 111, 4, 215, 98, 121, 84, 107, 249, 53, 126, 93, 127, 201, 199, 33, 29, 24, 71, 15, 5, 69, 217, 152, 2, 17, 0, 0, 0, 4, 202, 176, 111, 0, 0, 0, 0, 1, 0, 0, 10, 23, 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