Crowd TT Explorer- Prettify

Crowd TT Explorer- Utility Tool- Prettify: Parse and format wallet transaction timestamps into human-readable formats

Overview

This node, named "Crowd TT Explorer- Prettify," is designed to process wallet transaction data by parsing and formatting transaction timestamps into various human-readable date/time formats. It is useful when you have raw transaction data with timestamps (in Unix epoch seconds) and want to convert these timestamps into more understandable formats for reporting, display, or further processing.

Common scenarios include:

Transforming blockchain or wallet transaction logs into readable date/time formats.
Selecting specific transactions based on time criteria (e.g., earliest, latest).
Preparing transaction data for dashboards or user interfaces where human-friendly dates are required.

For example, if you receive a list of wallet transactions each with a timestamp, this node can output those transactions enriched with ISO 8601, UTC, local, and custom formatted date/time strings.

Properties

Name	Meaning
Process Mode	How to select which transactions to process from the input: - All Transactions - First Transaction - Last Transaction - Latest by Time - Earliest by Time
Time Format Options	Which date/time formats to include in the output: - Include ISO Format (ISO 8601) - Include Local Format (local date/time string) - Include UTC Format (UTC string) - Include Custom Format (custom readable format like "December 1, 2023, 10:30:00 AM")

Output

The node outputs JSON objects representing processed transactions. Each output item corresponds to one transaction (or a selected subset depending on the Process Mode). The structure includes:

originalTime: The original timestamp value (Unix epoch seconds).
parsedTime: An object containing the formatted date/time strings according to the selected options:
- iso: ISO 8601 format string (e.g., "2023-12-01T10:30:00.000Z").
- utc: UTC string format (e.g., "Fri, 01 Dec 2023 10:30:00 GMT").
- local: Localized date/time string.
- dateOnly: Localized date only string.
- timeOnly: Localized time only string.
- custom: A custom formatted string (e.g., "December 1, 2023, 10:30:00 AM").
readableTime: A single string representing the most readable time format available, prioritizing custom, then local, then ISO.
All other original properties of the transaction are preserved.

If multiple transactions are processed (Process Mode = "all"), each transaction is output as a separate item paired with its original input item index.

The node does not output binary data.

Dependencies

No external services or APIs are required.
The node relies on JavaScript's built-in Date object for timestamp parsing and formatting.
No special environment variables or credentials are needed.

Troubleshooting

Error: Could not find transaction array in item X
This error occurs if the input data structure does not contain an array of transactions as expected. The node expects either an array directly in item.json or nested inside item.json[0]. Ensure your input data matches this structure.
Error: No transactions found in item X
This means the transaction array was found but is empty. Verify that your input contains actual transaction entries.
General processing errors
If the timestamp field (time) is missing or not a valid number, the node may throw errors during date parsing. Make sure each transaction has a valid numeric timestamp.
Incorrect time zone or format issues
The node uses the system locale and timezone for local and custom formats. If results appear unexpected, check the environment's locale settings.