Just eyeballing the the number of purchased tickets at dcrstats makes the current price seem a little bit off. ... or am I crazy? On a related not the dcrstats mempool figure is stuck at 20. That must be a bug.
The price is accurate. We can see by looking at the number of relative changes to the pool size in the last 10 intervals and the current pool size that the number of tickets purchased has exceeded the number voting and thus the pool size is roughly 1.2% over target and the price must rise to compensate. This is what happens when stake participation rises as it has been doing. The price adjusts upwards to compensate for the influx of new coins. Code: relative pool changes: [-12,319,-49,477,133,-81,-85,24,-93,-184] current pool size: 41447 (from target: 1.188%)
Thanks for the confirmation that everything is OK! Someone mentioned the high price at Bitcointalk and I noticed my autobuying had stopped (my limit set at 65).