Nostrfi
/Docs
Browse documentation
Owner: NostrfiLast reviewed: 2026-11-12

Event browser

What it is

The Events page of the admin dashboard, at /admin/dashboard/events, lets you look through the events the relay has stored. You fill in a filter, run the query, and open any result to see the full event, with its signature checked in your browser.

This page describes relay 0.2.0 and later.

The event browser: filters for kinds, author, event ID, content, time, and two tag rows for the t tag, above a table of matching eventsThe event browser: filters for kinds, author, event ID, content, time, and two tag rows for the t tag, above a table of matching events
Two t rows: events with either hashtag. Each query costs one signature.

The filters

Every field is optional. Leave everything blank to see the newest events.

FieldWhat to enterMatches
KindsKind numbers separated by commas, for example 1, 7Events of any of those kinds
AuthorA hex pubkey, or at least its first four charactersEvents signed by that key
Event IDA hex event ID, or at least its first four charactersThat event
Content containsAt least 3 charactersEvents whose content contains the text, ignoring case
From / ToA date and time, in your browser's timezoneEvents created in that range, inclusive
TagsOne or more tag rows (see below)Events carrying those tags

Author and event ID take hex only, not npub or note strings.

Tag rows

Each tag row has a tag name, picked from the supported tags, and an optional value.

  • Add Tag adds another row.
  • The trash button removes a row.
  • Clear filters empties every field and leaves one empty tag row.

A row with no tag name is ignored. A value with no tag name is an error, and the page asks you to choose a tag.

How rows combine

  • Different tag names must all match. A t row and a client row find events that have both.
  • Rows with the same tag name are alternatives. Two t rows find events with either hashtag. This is how NIP-01 filters treat several values for one tag.
  • A value is compared with the tag's first value, exactly, including case. For ["t", "nostr"] that is nostr.
  • Tags combine with the other fields the same way. Kinds 1 and a t row find kind 1 events with that hashtag.

Leaving the value blank

A row with a blank value matches every event that carries the tag, whatever its value. This is the only way to find tags that have no value, such as the NIP-70 - tag on protected events.

If one row for a tag name is blank, other rows for the same name add nothing: "has a t tag, or has t = nostr" is just "has a t tag".

Running a query

Nothing runs as you type. Press Run query when the filter is ready.

Each query is a call to the relay's operator API, so your signer is asked to sign it, once per query. A query returns up to 100 events, newest first. Load more fetches the next 100 and costs another signature. See why actions ask your signer.

Expired events and events banned through moderation are never returned.

Examples

To findKindsTag rows
Notes published from one client1client = amethyst
Posts with either of two hashtagst = nostr, and t = relays
Every protected event- with the value left blank
Reactions to one event7e = the event's hex ID
Everything that mentions a pubkeyp = the hex pubkey

Client names in client tags are whatever the client writes, so check the exact spelling on one of its events first.

Supported tags

The relay lets you filter by these tags. It refuses any other name, so the tag picker offers only these.

TagDescriptionDefined in
aReferences an addressable or replaceable eventNIP-01
altHuman-readable summary for custom event kindsNIP-31
dUnique identifier for addressable eventsNIP-01
eReferences another eventNIP-01
gGeographic location as a geohashNIP-52
hGroup in the relay-based groups systemNIP-29
iExternal identities and content identifiersNIP-39, NIP-35, NIP-73
pReferences a user's public keyNIP-01
qReferences an event in a quote repostNIP-18
rankRanking score (0-100) for trusted assertionsNIP-85
rReferences a URL or relay addressNIP-24, NIP-65
tHashtagNIP-24
-Protected event, publishable only by its authorNIP-70
clientClient application that published the eventNIP-89
emojiCustom emoji used in the contentNIP-30
imetaMetadata about media URLs in the contentNIP-92
proxySource of the event on another protocolNIP-48
zapRecipients of Lightning payments (zaps)NIP-57

Limits

  • Older events can't match multi-letter tags. Events stored before the relay kept every event's full tags (schema version 3) were saved with single-letter tags only, so a client, alt, or other multi-letter row never finds them. See tag fidelity.
  • Multi-letter tag filters are an operator feature. Public REQ subscriptions from Nostr clients still filter stored events by single-letter tags only, as NIP-01 defines. Only the dashboard and the operator events API can filter by tags such as client or -.

The API behind it

The Events page is a client of the relay's operator events API, POST /api/events/query, which you can also call yourself with a NIP-98 signature. Its request fields and responses are documented in the relay's README.