npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

neo-n3-watch

v1.0.0

Published

Real-time Neo N3 contract event monitor — stream on-chain notifications to your terminal

Readme

neo-n3-watch

Real-time Neo N3 contract event monitor. Stream on-chain notifications straight to your terminal — no node setup, no code, just npx.

── Block 4821903 ───────────────────────────
  TX       0xabc123...
  Contract 0xef4073a0f2b305a38ec4050e4d3d28bc40ea63f5
  Event    Transfer
  Args
    [0] Hash160  = 0xd2a4cff31913016155e38e474a2c06d08be276cf
    [1] Hash160  = 0x0000000000000000000000000000000000000000
    [2] Integer  = 100000000

Why

Every Neo N3 dApp developer eventually needs to watch contract events while testing — but doing it today means either writing custom RPC polling code, running a full indexer, or staring at a block explorer. neo-n3-watch gives you a focused, zero-setup event stream in your terminal in one command.

Install

npm install -g neo-n3-watch

Or run without installing:

npx neo-n3-watch --contract 0xef4073a0f2b305a38ec4050e4d3d28bc40ea63f5

Usage

neo-n3-watch [options]

Options

| Flag | Description | Default | |------|-------------|---------| | -c, --contract <hash> | Filter by contract script hash | all contracts | | -e, --event <name> | Filter by event name (e.g. Transfer) | all events | | -n, --network <name> | mainnet or testnet | mainnet | | --rpc <url> | Custom RPC node URL (overrides --network) | — | | -p, --poll <ms> | Polling interval in milliseconds | 2000 |

Examples

Watch all NEO token transfers on mainnet:

neo-n3-watch --contract 0xef4073a0f2b305a38ec4050e4d3d28bc40ea63f5 --event Transfer

Watch all events from any contract on testnet:

neo-n3-watch --network testnet

Watch a custom contract with fast polling:

neo-n3-watch --contract 0xYOUR_CONTRACT_HASH --network testnet --poll 1000

Use a custom RPC node:

neo-n3-watch --rpc https://your-node.example.com:443 --contract 0xYOUR_CONTRACT_HASH

Default RPC Nodes

| Network | URL | |---------|-----| | mainnet | https://mainnet1.neo.coz.io:443 | | testnet | https://testnet1.neo.coz.io:443 |

How It Works

neo-n3-watch polls getBlockCount on the Neo N3 RPC every --poll milliseconds. For each new block it fetches all transactions and their ApplicationLog, then filters notifications by contract hash and/or event name and pretty-prints them to your terminal.

No indexer. No database. No websocket. Just RPC polling — lightweight and works with any public Neo N3 node.

Known Limitations

  • Relies on RPC polling (not WebSocket push), so minimum latency equals the block time (~15s on mainnet)
  • The RPC node must have the ApplicationLogs plugin enabled (all public COZ nodes do)
  • Very high-volume contracts may produce a lot of output — use --event to narrow the stream

License

Apache 2.0 — see LICENSE

Contributing

PRs welcome. Open an issue first for bigger changes.