How to Screen Multiple TRON Wallets with a CSV

1. Prepare a small, explicit intake file

Use one TRON public address per row. Include an address header; label and reference_id are optional context for your desk. Keep labels short and use internal trade references rather than personal details. Remove accidental duplicate rows before upload; do not assume the importer deduplicates them.

The current browser upload accepts at most 500 data rows and 500,000 characters of CSV content. Start with a small file to confirm your format. Standard quoted cells can contain commas, but avoid multiline cells because the importer reads the file line by line.

address,label,reference_id
<TRON_PUBLIC_ADDRESS>,Counterparty A,OTC-001
<TRON_PUBLIC_ADDRESS>,Counterparty B,OTC-002

2. Create the job and resolve invalid input

In Batch, download the CSV template if needed, then choose a file or paste its contents. Review the valid and invalid counts and the row preview before creating the batch. An invalid address remains an invalid row; it is not a negative screening result.

Open the job row details or export its CSV to inspect row-level errors and compare them with the input. Correct an address from the original source rather than guessing characters. Submit corrected rows in a new job. Keep valid rows from the original job separate so you do not unintentionally repeat work.

3. Process the queued rows and check completion

Start processing the job. Each request handles up to 25 queued rows and the browser continues while queued rows remain. Pause stops after the current request; resume continues queued rows. Keep this page open for continuous processing. If a request fails, review the message and resume when ready; failed rows remain visible for review. Creating a job alone does not complete it, and a 500-row upload does not mean 500 simultaneous checks.

The browser Batch workflow requires an account and working persistence. Its current processing route does not deduct deep-check credits. Batch screening uses its own source checks and is not equivalent to running the full deep exposure analysis on every wallet. A separate deep check uses the normal credits described on Pricing; machine API entitlements may differ.

4. Review the export, including failures

Select Export CSV and review row status, error, and available screening fields. A completed job with errors can contain useful results alongside invalid or failed rows. A failed lookup must remain unresolved in your intake process, rather than becoming a clean result by omission.

Use single-address screening when a row needs detailed follow-up. Keep the batch export with your intake reference and record any separate deep reports. Batch results reflect the sources and coverage at processing time; they do not establish identity, provide continuous monitoring, or predict future freezes.

1. Reconcile exported row counts with the original intake.
2. Separate completed rows from invalid and failed rows.
3. Review positive findings and source limitations under your desk's policy.
4. Correct or re-check unresolved rows and document their disposition.