Flaky tests can make automated software testing unreliable due to their unpredictable behavior. These tests can pass or fail on multiple runs on the same codebase. However, flaky tests often do not refer to any fault, even though they can make the continuous integration (CI) pipeline fail. A common type of flaky test is the order-dependent (OD) test. The outcome of an OD test depends on the order of its running with respect to other testcases. Several studies have explored the detection and repair of OD tests. However, their methods require multiple re-runs of tests unrelated to the order dependence. Hence, prioritization of potential OD tests is necessary to reduce the re-runs. In this paper, we propose a method to prioritize potential order-dependent tests. By analyzing shared static fields in test classes, we identify tests that are more likely to be order-dependent. In our experiment on 27 projects, our method correctly prioritized all OD tests in 23 projects, reducing the number of test executions by 65.92% on average and cutting re-runs by 72.19%. Our findings show that this approach can make OD test detection more effective in terms of execution cost.