Token Dashboard
tokens
3763
contracts
11899
confirmed
10116of 11899
chains
15
unmeasured
51
queued
0

Pin #1570

? → ?
receivedrejected · BLOCKED
token
no symbol
bridge
—
token entity
—
bridge tx
—
delivery tx
—

What happened to this pin

pin received
2026-09-02 08:18:18 UTC · 2 mo ago · #1570 from the feed
rejected by ingest
2026-09-02 08:18:18 UTC · 2 mo ago · BLOCKED
received
2026-09-02 08:18:18 UTC · 2 mo ago
verdict
rejected · BLOCKED
labels
deployer_burst
priority
high
identity
base:0x39265b5a6fcf1c84bc95236d54c69cf263ff867f830b5a7998cb330fa1a5a35b:615

The contract was blocked outright. The pin is kept as a tombstone so the refusal stays countable.

A rejected pin never reaches discovery — unless you accept it. Lifts the block on this contract, so this pin and any future pins for it go through.

Overrule ingest for this record and run discovery on it.

The record, as the feed sent it
feed id—
transfer id—
status—
bridge—
source— · —
source tx—
source block— · —
destination— · —
destination tx—
destination block— · —
token—
symbol · name · decimals— · — · —
known as—
amount sent · received— · —

raw payload

{
  "note": "payload removed by operator block",
  "chain": "base",
  "address": "0x5576d6ed9181f2225aff5282ac0ed29f755437ea",
  "blocked": true
}