Your practice record

Your practice dashboard is everything you have done on /problems, in four tabs. A shorter version of it rides in the sidebar of the problem list itself, so you do not have to leave to see where you are.

Tab	What it holds
Overview	Your Practice Score and rank, three "next best problems", Revisits due, a skill map of every topic, the solved ring, languages and the activity graph
Submissions	Every submission you made, filterable by verdict, language and day
Score	Your score, your rank week by week, what each solved problem earns, and every change to the score
Lists	Starred, Revisit and lists you make yourself

Every number is a link: the solved count opens the list of problems you solved, a language opens your submissions in it, a day on the graph opens that day's submissions, and a topic on the skill map opens its unsolved problems. How the score itself works is on how scoring works.

Next best problems and Revisit#

Next best problems are three unsolved problems from three of your weakest topics, each one you have about a 65% chance of solving: hard enough to teach you something, easy enough to finish. They change once a day, not on every reload.

Revisit brings back problems you solved with help, or after four or more Submits, at 3, 7 and 21 days. Solving one again without help and without pasting your old code moves it to the next step; after all three it leaves the list. If you had help the first time, a clean Revisit solve at least a week later restores the problem's full points.

The solved ring#

How many problems you have solved, split into Easy, Medium and Hard, each against how many are published at that difficulty.

A solve is counted from a non-stale accepted submission. If a problem's test cases were later corrected, submissions judged against the old set stop counting - see verdicts and test cases.

Your practice streak#

Your practice streak counts days (India time) with at least one accepted Submit. Runs, AI help and project pushes do not keep it alive: it measures solving, not activity.

One missed day each week (Monday to Sunday) is forgiven automatically, so a single busy day does not end a long streak. If you have already used this week's forgiven day and have not solved anything today, the dashboard says so: "Solve one today to keep your 9-day streak". Today never breaks a streak on its own, because the day is not over.

The activity graph#

The contribution graph on this page is not a practice-only graph. It is your account-wide coding activity - the same rows drawn on your projects dashboard and on your public profile.

That is on purpose. Two graphs would each understate how much you actually code, on a platform whose pitch is one coding identity. So a day you spent in the editor and a day you spent on problems land in the same picture, and the practice-specific counts sit beside it rather than being carved out of it.

A cell counts runs, AI actions, pushes and submissions. Days with no activity are genuinely empty rather than missing.

Your submissions#

Every submission you have made, across all problems, newest first - problem, verdict, language, runtime and when. The Submissions tab filters by verdict, language and day, keeps the filters in its address so a link reopens the same view, and each row opens the submission with its result.

This is the account-wide view; a single problem's own Submissions tab shows just that problem's.

Is this a credential?#

No, and we do not present it as one.

Your record is a record for you. We cannot tell whether a solution was written by you or pasted from somewhere else, and chasing that would make the product worse for everyone without ever working. So anything we say about it describes activity - how many problems you have solved, and a score weighted by how hard they were - and we never imply a verification we do not perform.

The value is real regardless: it is a truthful account of what you have actually done, which is what makes "you have not touched binary search in three weeks" possible.

Related#