uPlexa Block Explorer

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

Tx hash: 6f2ead665de4c0d5f4591fa60481fa799f74f326b3420d1f0188ea7f4afebb92

Tx prefix hash: 0505c2b4e6389892dcd89c8a53de61ff7cd05717cb863c4f610fda14c9a9844b
Tx public key: fc2ffa395ac6297bf2e1c79a00258def1884dcf1dee2070ea2b2cd51d4b0fc0c
Timestamp: 1593489715 Timestamp [UCT]: 2020-06-30 04:01:55 Age [y:d:h:m:s]: 00:002:05:22:22
Block: 469751 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 1611 RingCT/type: yes/0
Extra: 01fc2ffa395ac6297bf2e1c79a00258def1884dcf1dee2070ea2b2cd51d4b0fc0c021100000001b091310000000001000001fd00

1 output(s) for total of 1964.19 upx

stealth address amount amount idx
00: d49fb6fe2bd22adb632e2cad66caf2eb8f211b6451114c57c0b0437d128e7e44 1964.19 2531948 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": 469811, "vin": [ { "gen": { "height": 469751 } } ], "vout": [ { "amount": 196419, "target": { "key": "d49fb6fe2bd22adb632e2cad66caf2eb8f211b6451114c57c0b0437d128e7e44" } } ], "extra": [ 1, 252, 47, 250, 57, 90, 198, 41, 123, 242, 225, 199, 154, 0, 37, 141, 239, 24, 132, 220, 241, 222, 226, 7, 14, 162, 178, 205, 81, 212, 176, 252, 12, 2, 17, 0, 0, 0, 1, 176, 145, 49, 0, 0, 0, 0, 1, 0, 0, 1, 253, 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