Someone launched a token using the ssych name. There is no ssych token, and ssych is not connected to it. Don't buy it.

UI

Benchmark

The order book, candlestick and trade tape on a live feed, measured in your browser while you watch. SVG only, no chart library, no sign up.

At 60 updates a second from a 10,000 point feed, the trade tape held 59 frames a second and the order book 60, on a server with no GPU.

Measured on headless Chromium 151 on Linux, an Azure D16ps v5 server (16 Arm Neoverse N1 cores, no GPU), 9 November 2026. Run the same tests on your device below.

TestPointsRateFramesUpdate cost p95
Trade tape10,00060/s59 fps6.7 ms
Trade tape50,00060/s32 fps23.6 ms
Order book10,00010/s60 fps6.0 ms
Order book10,00060/s60 fps3.7 ms
Order book50,00060/s60 fps6.7 ms
Candlestick1,00010/s52 fps38.9 ms
Candlestick1,00060/s28 fps41.2 ms

Frames per second

56

Frame time p50

16.7 ms

Frame time p95

33.3 ms

Updates per second

56

Update cost p95

9.5 ms

Data points

10,000

DOM nodes

78

JS heap

20 MB

Your device: Headless Chromium 151, Linux, 16 threads, 32 GB or more

Trade tape10,000 prints, the newest 12 drawn
TimePriceSize
14:30:42228.4131
14:30:42228.4821
14:30:41228.4817
14:30:41228.53146
14:30:41228.5584
14:30:41228.5811
14:30:40228.63243
14:30:40228.583,681block
14:30:40228.643,900block
14:30:40228.6636
14:30:39228.60112
14:30:39228.63220
14:30:39228.57175

How each number is measured

The components are the ones you install, unchanged. The page only feeds them seeded data. Charts are hand written SVG with no chart library.

Frames per second
Frames in the last 5 seconds ÷ 5. The first second after any change is left out.
Frame time p50, p95
The gap between two frames (requestAnimationFrame), median and 95th percentile over the same window.
Updates per second
Feed updates applied in the window ÷ its seconds. Each one is a new array handed to the component.
Update cost p95
React's render and commit of one update, timed around flushSync, 95th percentile.
Data points
Book levels, candles and prints the components on screen read.
DOM nodes
Elements inside the test area.
JS heap
performance.memory, reported by Chromium browsers only.