Logged VPIN data appears to be averaged?

Interesting one to get a perspective on - I have a VPIN connected to a LED and the hardware either sends 0 or 255 always upon a change. I added it to a Super Chart today and found strange values, almost what appears to be a moving average. I downloaded the data via the API to have a look and this is what I see, any ideas?

0	1516973880000
0	1516973940000
0	1516974000000
0	1516974060000
0	1516974120000
0	1516974180000
0	1516974240000
0	1516974300000
63.75	1516974360000
0	1516974420000
0	1516974480000
0	1516974540000
63.75	1516974600000
6.375	1516974660000
0	1516974720000
0	1516974780000
108.375	1516974840000
63.75	1516974900000
0	1516974960000
0	1516975020000
0	1516975080000
0	1516975140000
0	1516975200000
0	1516975260000
0	1516975320000
0	1516975380000
0	1516975440000
0	1516975500000
0	1516975560000
89.25	1516975620000
0	1516975680000
0	1516975740000
0	1516975800000
222.3076923077	1516975860000
0	1516975920000
0	1516975980000
57.375	1516976040000
0	1516976100000
63.75	1516976160000
229.5	1516976220000
210.375	1516976280000
121.125	1516976340000
0	1516976400000
51	1516976460000
0	1516976520000
44.625	1516976580000
0	1516976640000
0	1516976700000
0	1516976760000
0	1516976820000
0	1516976880000
0	1516976940000
0	1516977000000
0	1516977060000
0	1516977120000
0	1516977180000

This averaging (granularity) is mentioned in the Docs (and throughout this forum) for the older History Graph… but is also applicable to the Super Chart. I believe it is done this way to minimise Blynk Server storage and load.

As to what you are seeing, it is time/date stamps in UI format along with the actual (well, averaged) data reads of the vPin.