Query Builder Codes

​

Where Builder Code data lives

• Deduplicate transactions. In base.transaction_attributions a transaction attributed to multiple Builder Codes appears once per code, so count DISTINCT transaction_hash when you want a transaction count.
• Scope to active rows. Both tables use an action column (Int8): 1 means the record was added to the chain and -1 means it was removed by a re-org. Filter action = 1 for a quick view, or aggregate with SUM(action) > 0 if you need re-org-safe totals.

​

Access

​

Example queries

​

EOA transactions for a Builder Code

SELECT transaction_hash, block_number, block_timestamp
FROM base.transaction_attributions
WHERE builder_code = 'your_builder_code'
  AND action = 1
ORDER BY block_timestamp DESC
LIMIT 100;

​

User operations for a Builder Code

SELECT user_op_hash, transaction_hash, sender, block_timestamp, success
FROM base.decoded_user_operations
WHERE has(builder_codes, 'your_builder_code')
  AND action = 1
ORDER BY block_timestamp DESC
LIMIT 100;

​

Daily attributed transaction count

SELECT
  toDate(block_timestamp) AS day,
  COUNT(DISTINCT transaction_hash) AS transactions
FROM base.transaction_attributions
WHERE builder_code = 'your_builder_code'
  AND action = 1
GROUP BY day
ORDER BY day DESC;

### Total attributed activity across EOAs and user operations

Combine both surfaces into a single count of distinct attributed transactions:

```sql
SELECT SUM(transactions) AS total_attributed_transactions
FROM (
  SELECT COUNT(DISTINCT transaction_hash) AS transactions
  FROM base.transaction_attributions
  WHERE builder_code = 'your_builder_code'
    AND action = 1

  UNION ALL

  SELECT COUNT(DISTINCT transaction_hash) AS transactions
  FROM base.decoded_user_operations
  WHERE has(builder_codes, 'your_builder_code')
    AND action = 1
);

​

Query tips

1. Match the right column per table — filter builder_code = '...' on base.transaction_attributions and has(builder_codes, '...') on base.decoded_user_operations.
2. Deduplicate transactions — a transaction attributed to multiple codes appears once per code in base.transaction_attributions; count DISTINCT transaction_hash.
3. Scope to active records — add action = 1 for a quick view, or SUM(action) > 0 in a HAVING/aggregate for re-org-safe totals.
4. Bound your scan — filter on block_timestamp and add a LIMIT while iterating to keep queries fast.

​

Learn more

• Builder Codes overview — what Builder Codes are and how to register
• Schema reference — full column definitions for base.transaction_attributions and base.decoded_user_operations
• Quickstart — run your first SQL API query
• Best practices — write fast, correct SQL API queries