# Transaction trails around a curved ledger > A dark investigation dashboard pairs a sweeping ledger arc with dense white network traces, yellow connections and a red triangular marker. Compact charts and tables form a technical instrument panel beneath the main visualization. - Kind: Video - Page: https://meetreference.com/v/video-transaction-trails-around-a-curved-ledger-433f16/ - Ready-to-use agent handoff: https://meetreference.com/v/video-transaction-trails-around-a-curved-ledger-433f16/agent.txt - Exact prompt as plain text: https://meetreference.com/v/video-transaction-trails-around-a-curved-ledger-433f16/prompt.txt - Authorship: Not stated - Made with: Not stated - Model: not stated - Built with: not stated - Style: Data stories; technical, radial, monochrome, high-density, dashboard, sci-fi - Length and format: 23 sec, 4:5 (720x900 source) - Playback: a muted visual reference. The original soundtrack is available only at the source. - Shared by @immortalhowwl in X, Oct 13, 2026: https://x.com/immortalhowwl/status/2110120519395688758 - Prompt fidelity: Verbatim. This is the complete prompt exactly as the creator published it. ## Before you start Guidance from Reference, separate from the creator's instructions. 1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present. 2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized. 3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed. 4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting. 5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use. ## Recreating this video These are the creator's published instructions, unedited. ## Prompt ```text 1. Investigate how a selected tool that I am authorized to inspect identifies buys, sales and transfers. 2. Write a specification with source-file references and missing details. Build an independent implementation and tests. 3. Connect public Solana transactions. Group purchases of the same token by watched wallets within a five-minute window, then show each participant’s later observed sales. 4. Link every finding to its transaction. Show incomplete history and errors separately. Never conclude ‘still holding’ just because no sale was found.” ``` ## What it looks like Written by Reference from the video frames, not by the creator. Futuristic memecoin-trading interface featuring a dense transaction trail, a highlighted central marker, and compact analytics. - Color: Near-black and charcoal with muted gray data, lime-yellow connector lines, red highlights, and occasional cyan or gold accents. - Type: Small, condensed sans-serif labels and technical-looking data text in a high-density interface. - Framing: A large central visualization dominates the screen: branching network lines occupy the left, a curved band of data sits near the middle, and horizontal information blocks fill the right. A grid of smaller analytics panels runs along the bottom. - Structure: Thin top navigation bar, expansive transaction visualization, and a bottom strip of boxed charts, tables, and status indicators. Storyboard, nine frames spread across the video: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/storyboard.webp - Frame 1 at 1.3s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f1.webp - Frame 2 at 3.8s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f2.webp - Frame 3 at 6.4s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f3.webp - Frame 4 at 8.9s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f4.webp - Frame 5 at 11.5s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f5.webp - Frame 6 at 14.1s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f6.webp - Frame 7 at 16.6s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f7.webp - Frame 8 at 19.2s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f8.webp - Frame 9 at 21.7s: https://meetreference.com/media/video-transaction-trails-around-a-curved-ledger-433f16/f9.webp ## Links - Watch: https://x.com/immortalhowwl/status/2110120519395688758 - Original post: https://x.com/immortalhowwl/status/2110120519395688758 - Discovery collection: https://data.openchamber.dev/opus-5-5-videos/v/immortalhowwl-2110120519395688758