uPlexa Block Explorer

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

Tx hash: 552b9b2dbe8a8c4e9a48b34c8e214c5a9ba4415776dc72cda2143ee227f64607

Tx prefix hash: dc6f3b9c9d88040b4bea29e6203d1f955ab8c61f21ff38b32f2a5b2ccdde51a0
Tx public key: 3d2eca526a17d8178640224e41061dd974eead731f8ce7d9fd067b093ae61012
Timestamp: 1602971901 Timestamp [UCT]: 2020-10-17 21:58:21 Age [y:d:h:m:s]: 00:004:08:13:57
Block: 548842 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 3125 RingCT/type: yes/0
Extra: 013d2eca526a17d8178640224e41061dd974eead731f8ce7d9fd067b093ae610120211000000433a89b400000000000000000000

1 output(s) for total of 1927.50 upx

stealth address amount amount idx
00: 95627ec9c54b9ad08aefe0d1e53a712abf50ef2bc818c9e2b51701c393379731 1927.50 2871402 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": 548902, "vin": [ { "gen": { "height": 548842 } } ], "vout": [ { "amount": 192750, "target": { "key": "95627ec9c54b9ad08aefe0d1e53a712abf50ef2bc818c9e2b51701c393379731" } } ], "extra": [ 1, 61, 46, 202, 82, 106, 23, 216, 23, 134, 64, 34, 78, 65, 6, 29, 217, 116, 238, 173, 115, 31, 140, 231, 217, 253, 6, 123, 9, 58, 230, 16, 18, 2, 17, 0, 0, 0, 67, 58, 137, 180, 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