Unlock calendar
Locked, not burned
473,606,530.96 $LAZYPOS sat in 14 funded escrows (15 lock records) in the Nov 11, 2026, 1:51 PM CST snapshot: 53.6378% of remaining supply.
| Month | $LAZYPOS becoming claimable | Large single events |
|---|---|---|
| Nov 2026 (after Nov 11) | 108,410,160.87 | 100M (F9py) |
| Dec 2026 | 63,455,214.58 | 50M (51EH) |
| Jan 2027 | 13,611,378.99 | — |
| Feb 2027 | 13,163,547.75 | — |
| Mar 2027 | 13,746,881.42 | — |
| Apr 2027 | 13,163,547.75 | — |
| May 2027 | 13,903,045.82 | — |
| Jun 2027 | 59,788,547.92 | 50.5M (Fi5k) |
| Jul 2027 | 5,694,712.32 | — |
| Aug 2027 | 5,538,547.92 | — |
| Sep 2027 | 5,538,547.92 | — |
| Oct 2027 | 4,194,711.07 | — |
| Nov 2027 | 4,038,546.67 | — |
| Dec 2027 | 4,038,546.67 | — |
| Jan 2028 – Oct 2033 | 145,320,593.31 | includes 50.5M (Fi5k) |
| Total | 473,606,530.96 | Equals current lock vaults. Eligibility is not a claim or a sale. |
Every lock
| Lock page | Vault (Nov 11) | Claimed (Nov 11) | Total | Schedule | First eligibility after Nov 11 cutoff | Final eligibility | Recipient |
|---|---|---|---|---|---|---|---|
| 83WK…6hBq | 5,833,337.50 | 1,166,667.50 | 7,000,005 | 12 releases of 583,334, every ~30.4167 days | Dec 8, 2026, 3:13 PM CST | Sep 8, 2027, 10:13 AM CDT | 74LS…US9p |
| X8AC…aqpz | 26,250,000 | 18,750,000 | 45,000,000 | 12 releases of 3,750,000, every ~30.4167 days | Dec 11, 2026, 5:19 AM CST | Jun 11, 2027, 6:19 PM CDT | 74LS…US9p |
| F8cf…cP1q | 18,366,666.67 | 633,333.33 | 19,000,000.00 | 60 releases of 316,667, every ~30.4167 days | Nov 12, 2026, 8:15 PM CST | Aug 12, 2031, 3:15 PM CDT | 74LS…US9p |
| Gg2F…HMyh | 56,531,513.79 | 468,493.21 | 57,000,007.00 | 365 releases of 156,164, weekly (7 days) | Nov 14, 2026, 12:40 PM CST | Oct 15, 2033, 1:40 PM CDT | 74LS…US9p |
| 9qZC…mZr3 | 4,583,337.92 | 416,667.08 | 5,000,005.00 | 12 releases of 416,667, every ~30.4167 days | Nov 16, 2026, 12:10 PM CST | Sep 16, 2027, 5:10 PM CDT | 74LS…US9p |
| 6UTq…C9zZ | 29,166,666.67 | 20,833,333.33 | 50,000,000.00 | 12 releases of 4,166,667, every ~30.4167 days | Nov 21, 2026, 3:30 PM CST | May 23, 2027, 4:30 AM CDT | 74LS…US9p |
| 4mEe…Vpyr | 5,500,004.58 | 500,000.42 | 6,000,005.00 | 12 releases of 500,000, every ~30.4167 days | Nov 23, 2026, 2:09 AM CST | Sep 23, 2027, 7:09 AM CDT | 74LS…US9p |
| 6RjC…wMc2 | 9,666,666.67 | 333,333.33 | 10,000,000.00 | 60 releases of 166,667, every ~30.4167 days | Nov 24, 2026, 4:35 PM CST | Aug 24, 2031, 11:35 AM CDT | 74LS…US9p |
| F9py…jkrG | 100,000,000 | 0 | 100,000,000 | One release | Nov 24, 2026, 8:30 PM CST | Nov 24, 2026, 8:30 PM CST | 2afN…E2Ds |
| 2uJK…CyXZ | 41,666,666.67 | 8,333,333.33 | 50,000,000.00 | 24 releases of 2,083,333, every ~30.4167 days | Nov 25, 2026, 6:30 PM CST | Jun 25, 2028, 5:30 PM CDT | 74LS…US9p |
| iwYe…goAo | 6,708,337.17 | 291,666.83 | 7,000,004.00 | 24 releases of 291,667, every ~30.4167 days | Nov 29, 2026, 10:30 PM CST | Sep 29, 2028, 3:30 AM CDT | 74LS…US9p |
| 8CJP…3MN1 | 18,333,333.33 | 1,666,666.67 | 20,000,000.00 | 36 releases of 555,556, every ~30.4167 days | Dec 3, 2026, 3:15 PM CST | Aug 3, 2029, 12:15 AM CDT | 74LS…US9p |
| 51EH…n7om | 50,000,000 | 0 | 50,000,000 | One release | Dec 4, 2026, 11:30 AM CST | Dec 4, 2026, 11:30 AM CST | Token mint 2pVm…pump * |
| Fi5k…fWU1 | 101,000,000 | 0 | 101,000,000 | 2 releases of 50,500,000, every 365 days | Jun 18, 2027, 8:40 AM CDT | Jun 17, 2028, 8:40 AM CDT | 74LS…US9p |
| 2aFv…UoHi | 0 | 50,000,000 | 50,000,000 | One release | None (schedule complete) | Oct 17, 2026, 10:00 AM CDT | 74LS…US9p |
Recipients. The 100,000,000 lock names wallet 2afN…E2Ds. Other funded locks, except the one below, name wallet 74LS…US9p.
*The Dec 4, 2026 lock. The recipient on this 50,000,000 lock is the token’s mint address (2pVm…pump), not a normal wallet. It stays counted as locked supply. It is not burned and not known to be permanently unrecoverable.
Schedules. “~30.4167 days” means a fixed 2,628,000-second interval, not calendar months. Lock 2aFv was fully claimed (50,000,000) before the snapshot and holds zero.
Jupiter Lock is the source of truth. This page is a dated snapshot and does not update by itself. Download the snapshot data (JSON).