uPlexa Block Explorer

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

Tx hash: de897a6b167b1fb6e4d54faf77585ff4be5805bbf1cdcb31b575844c1b377ae1

Tx prefix hash: af78a5d5094162b31bb433ed02cce773c0a9d18a4b9d793e26bac7c968ba066d
Tx public key: ada1c6a8dc88070e99b6b3e239c604f78adfe88c4a65ce76012b947ee237f109
Timestamp: 1605992276 Timestamp [UCT]: 2020-11-21 20:57:56 Age [y:d:h:m:s]: 00:011:14:05:21
Block: 573986 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 8355 RingCT/type: yes/0
Extra: 01ada1c6a8dc88070e99b6b3e239c604f78adfe88c4a65ce76012b947ee237f109021100000012126a7f00000000010000082b00

1 output(s) for total of 1915.98 upx

stealth address amount amount idx
00: 2ca6d1db917444a7fbad7c092ad79d64938b493c5b9bef062d02af3aefe99756 1915.98 2965486 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": 574046, "vin": [ { "gen": { "height": 573986 } } ], "vout": [ { "amount": 191598, "target": { "key": "2ca6d1db917444a7fbad7c092ad79d64938b493c5b9bef062d02af3aefe99756" } } ], "extra": [ 1, 173, 161, 198, 168, 220, 136, 7, 14, 153, 182, 179, 226, 57, 198, 4, 247, 138, 223, 232, 140, 74, 101, 206, 118, 1, 43, 148, 126, 226, 55, 241, 9, 2, 17, 0, 0, 0, 18, 18, 106, 127, 0, 0, 0, 0, 1, 0, 0, 8, 43, 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