uPlexa Block Explorer

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

Tx hash: 13da38ad2e1a3558688532709e1ce53093abe5cc2b890bf4420b80693988f804

Tx prefix hash: 18914424b9f3e3571dfd981e2a1c74e696231337c0f96428dcdbf9fb6ce91583
Tx public key: 01651073a2a311b497ef2a457b347e015e37b86253ae2be1115b433d3846e534
Timestamp: 1605991954 Timestamp [UCT]: 2020-11-21 20:52:34 Age [y:d:h:m:s]: 00:011:13:21:09
Block: 573983 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 8333 RingCT/type: yes/0
Extra: 0101651073a2a311b497ef2a457b347e015e37b86253ae2be1115b433d3846e534021100000002126a7f00000000010000034b00

1 output(s) for total of 1916.58 upx

stealth address amount amount idx
00: fc2f30a1c47892df9c08706820f57915df5d69d0a11e2e4795644339b6542dc2 1916.58 2965473 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": 574043, "vin": [ { "gen": { "height": 573983 } } ], "vout": [ { "amount": 191658, "target": { "key": "fc2f30a1c47892df9c08706820f57915df5d69d0a11e2e4795644339b6542dc2" } } ], "extra": [ 1, 1, 101, 16, 115, 162, 163, 17, 180, 151, 239, 42, 69, 123, 52, 126, 1, 94, 55, 184, 98, 83, 174, 43, 225, 17, 91, 67, 61, 56, 70, 229, 52, 2, 17, 0, 0, 0, 2, 18, 106, 127, 0, 0, 0, 0, 1, 0, 0, 3, 75, 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