How to Check LP Unlock Date Before You Trade
Learn how to check LP unlock date on-chain, verify the locker and LP position, and assess liquidity withdrawal risk before first interacting with a token.

A token can show deep liquidity at the moment you inspect it and still face a major liquidity event hours later. That is why learning how to check LP unlock date is more useful than accepting a project’s claim that liquidity is “locked.” The useful question is not whether a lock exists. It is whether the relevant liquidity position is actually locked, who can redeem it, how much liquidity it represents, and when that control changes.
A liquidity lock can reduce one common rug-pull path: a team removing trading liquidity from a decentralized exchange pool. It does not prove that the token contract is safe, that selling is possible, or that supply cannot be inflated. Read the contract before you act, and treat liquidity evidence as one part of a broader on-chain review.
What an LP unlock date actually means
On automated market makers, liquidity providers deposit two assets into a pool. In return, they receive a claim on that position. On older constant-product pool designs, that claim is often represented by fungible LP tokens. On newer concentrated-liquidity designs, it may be represented by an NFT position with a chosen price range.
An LP unlock date is the time after which the party controlling that LP token or liquidity-position NFT can withdraw it from a third-party locker or vesting contract. Once redeemed, the owner may remove some or all of the underlying assets from the pool, subject to the pool’s mechanics and any additional restrictions.
That date is not a prediction that liquidity will be removed. It is a change in control. Before the date, a properly implemented lock may prevent withdrawal. After it, the holder can typically decide what to do with the position. For token holders, this distinction matters because a sudden liquidity reduction can make trading difficult, increase price impact, or leave a pool with little meaningful exit liquidity.
How to check LP unlock date on-chain
Start with identity, not a token name or ticker. Copy the canonical token contract address from a trusted source, then identify the primary trading pool or pools. A token can have multiple pools across decentralized exchanges, and the pool with the largest displayed liquidity is not always the one that matters most for real trading.
1. Identify the relevant liquidity pool
Inspect the pool address and its reserves or position data. Confirm that the pool pairs the token you are researching with the expected counterasset, such as wrapped native currency or a stablecoin. Then determine which pool has material liquidity and trading activity.
Do not stop after finding one locked pool. A project may lock a small pool while retaining control of a larger, unlocked position elsewhere. Conversely, a modest pool may be locked while the market primarily trades through another venue. The evidence must match the pool that actually supports liquidity for the token.
2. Determine who holds the LP claim
For a traditional LP-token pool, check the LP token holder records. The key question is whether the LP tokens sit in a recognized locker contract, a burn address, a multisignature wallet, a deployer-controlled wallet, or another address.
For concentrated-liquidity pools, inspect ownership of the position NFT. Looking only for fungible LP tokens can produce a false conclusion because the liquidity may be controlled through an NFT instead. The position’s price range also matters: liquidity placed far outside the current trading price may be technically present but not active for current swaps.
A burn address can indicate that the LP claim is permanently inaccessible, but verify the address and transaction path. A wallet merely labeled “burn” by an interface is not enough evidence. A locker can be useful, but its contract and release conditions still need review.
3. Read the locker’s release conditions
If the LP claim is held by a locker, open the locker contract or its verified on-chain records and locate the lock entry. Record the token or NFT identifier, the amount locked, the beneficiary, and the release timestamp.
A credible lock record should establish four facts:
- The locked asset is the LP token or position connected to the pool you identified.
- The amount represents a meaningful share of that pool’s liquidity.
- The locker’s release timestamp is in the future and can be converted from Unix time correctly.
- The listed beneficiary or withdrawal recipient is consistent with the project’s disclosed control structure.
The timestamp should be evaluated in UTC first. Front ends may display local time, while contract calls and block explorers typically expose Unix seconds. For example, a value like `1735689600` is not meaningful until it is converted to a human-readable UTC date. Also check whether the lock is a single release or a vesting schedule with several tranches.
4. Compare the locked amount with total pool liquidity
A future unlock date has limited value if only a small fraction of the LP claim is locked. Compare the locked LP balance or position liquidity against the total supply of LP tokens or the pool’s total active liquidity.
The calculation is not always straightforward. With fungible LP tokens, the percentage can often be estimated from the locked LP balance divided by total LP supply. With NFT positions, you may need to assess each position’s liquidity contribution and whether it is active within the current price range. In both cases, a locker badge without an amount is incomplete evidence.
5. Look for other withdrawal paths
A lock can be real and still fail to cover the full risk. Check whether the project controls additional LP tokens, related position NFTs, or pools on other exchanges. Review recent transfers from deployer-linked wallets and observe whether liquidity has been added, removed, or moved shortly before your review.
Also distinguish pool liquidity from token supply controls. An owner with minting authority could create additional tokens and sell them into the market even if a particular LP position is locked. Transfer restrictions, blacklist functions, proxy upgradeability, and concentrated holder balances create separate risks that an LP date does not resolve.
Evidence that deserves caution
Treat these conditions as reasons to investigate further, not automatic proof of misconduct. A lock that expires soon may simply reflect a project’s stated schedule, but it creates a near-term change in liquidity control. A short lock should be read alongside the pool size, token distribution, and the wallet that will receive the LP claim.
Be careful with screenshots, dashboard badges, and social posts that state a lock duration without exposing the underlying pool and locker details. Interfaces can be stale, labels can be incomplete, and a lock can apply to an irrelevant or very small position. On-chain transaction history, holder records, contract state, and the actual timestamp provide stronger evidence.
The locker itself is part of the risk model. If its contract permits an administrator to alter lock terms, migrate assets, or use an emergency withdrawal function, the displayed date may not be the whole story. This requires contract-level interpretation, especially where proxy contracts or admin-controlled upgrades are involved.
A practical review workflow
For an unfamiliar token, capture a timestamped snapshot before interacting. Resolve the canonical contract address, identify material pools, establish who controls each LP claim, and record any lock expiry with the locked share of the relevant pool. Then review independent contract controls that could affect your ability to trade or the token’s supply.
This workflow is particularly important on fast-moving, low-cap markets, where liquidity can change between a social-media post and the next block. It also avoids a common mistake: treating “liquidity locked” as a single pass-or-fail signal rather than a set of verifiable conditions.
CryptoScanPro’s read-only scanner can help structure this due diligence by analyzing supported network-specific liquidity and contract-risk signals from a timestamped on-chain snapshot. Its findings should be read as evidence for further assessment, not as a guarantee of token safety or a substitute for a full smart contract audit.
A dated lock entry is most useful when you can trace it from the token’s real trading pool to the actual LP claim and the contract that controls release. If any link in that chain is unclear, keep investigating before you rely on the date.