Uniswap V3 Positions

One Parquet table with 44 columns: one row per IncreaseLiquidity, DecreaseLiquidity, Collect and Transfer event of the Uniswap V3 position NFT contract on Ethereum, 0xC36442b4a4522E871399CD717aBDD847Ab11FE88. The columns are those of our Ethereum events table, less Log_Pc.

The latest month holds about 121,000 rows, counted for 12 September to 11 October 2026: 43,540 collections, 29,173 transfers, 28,263 increases and 19,694 decreases. That is roughly 230 MB as Parquet, a rough estimate from the 17 rows of the sample files; exact figures arrive with the delivery manifest.

This listing covers the latest month. The same table since 4 May 2021, about 7.5 million rows over 1.38 million positions, is part of the Uniswap V3 Liquidity dataset.

Read Call_Signature_Name with Log_Signature_Name. mint with IncreaseLiquidity opens a new position, and the same call also emits a Transfer from the zero address. increaseLiquidity with IncreaseLiquidity adds to an existing position. decreaseLiquidity with DecreaseLiquidity removes liquidity, collect with Collect pays out owed tokens and fees, and burn with Transfer closes the NFT. From 4 to 10 October 2026, 3,975 increases came from mint and 2,200 from increaseLiquidity.

Arguments is a JSON array with one entry per decoded argument: its position, name, type and a value list. Addresses sit in the hex slot of that list without the 0x prefix, uint128 and uint256 amounts in the string slot as raw integers. The token id is the tokenId argument. Token amounts are in raw units, so divide by 10 to the power of the token decimals.

Filter on the tokenId argument. The open liquidity is the sum of the liquidity argument on IncreaseLiquidity rows minus the sum on DecreaseLiquidity rows, and the owner is the to argument of the latest Transfer row; the zero address means the NFT was burned. A position opened before the month you bought needs its earlier rows for a full total.

The position NFT contract's events carry the token id but not the pool or the ticks; those are on the pool event the same call caused. That table is in the Uniswap V3 Liquidity dataset; join it on Transaction_Hash where its Call_CallerIndex equals the position row's Call_Index. On 11 October 2026 all 683 increases, 522 decreases and 945 collections had a matching pool event.

Positions opened straight on a pool by a vault or a custom contract are left out, because they have no position NFT; they are in the Uniswap V3 Liquidity dataset. Approval events are left out. Events from failed transactions and reverted calls are left out. There are no USD or decimal-adjusted columns; amounts are the raw integers from the logs.

Decoded from Ethereum by our own indexer, then filtered at export. We ran the export for the blocks of our Ethereum events sample file of 20 December 2025: its 19 position rows matched that file in all 44 columns. For 20 September 2026 the row count equalled a plain count of the source, 2,883 rows, with no repeated row keys.

The liquidity argument is Uniswap's raw L value, not a token amount. A decrease only marks tokens as owed; they are paid on Collect, and a Collect pays owed principal and fees together, so fee income is collected minus decreased amounts. Fees earned but not yet collected do not appear in logs. Log_Index restarts in each call frame, so the row key is Transaction_Hash, Call_Index and Log_Index.

One line in DuckDB: SELECT * FROM read_parquet('univ3_position_events/*.parquet') LIMIT 10. Pandas works too: pandas.read_parquet(path). Arguments is a JSON string, so parse it with json_extract in DuckDB or json.loads in Python. The sample files open without credentials.

Refreshed daily with T+1 latency, so a purchase made today includes everything to yesterday. Delivered as Parquet named by block range, 50 blocks per file and sorted ascending, under a stable layout with a JSON manifest listing every file and its sha256. We prepare the files within 7 business days of purchase and email you the location. You choose at checkout where to collect them: a Requester Pays S3 bucket, downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only API key and no egress fees. Files stay available for 7 days from delivery. Enterprise orders can be delivered into your own S3, GCS or R2 bucket.