Token Dashboard
tokens
3818
contracts
12124
confirmed
10310of 12124
chains
15
unmeasured
51
queued
0

Pin #9310

arbitrum → base
receivedqueueddiscovered · 9 min
token
NTT
bridge
Portal
token entity
NTTits contracts and routes
bridge tx
0x55d0bd6b…b3b528on arbitrum
delivery tx
—on base

What happened to this pin

pin received
2026-09-06 13:59:18 UTC · 2 mo ago · #9310 from the feed
accepted by ingest
2026-09-06 13:59:18 UTC · 2 mo ago · priority high
discovery outcome
2026-09-06 14:08:12 UTC · 2 mo ago · DISCOVERED after 9 min
token
NTT — its contracts, routes and alerts are on its own page
received
2026-09-06 13:59:18 UTC · 2 mo ago
verdict
accepted
labels
—
priority
high
identity
arbitrum:0x55d0bd6b2d068dfd4e89336b11e59f315f6d25906be9db4101bf399366b3b528:0
outcome
DISCOVERED
processed
2026-09-06 14:08:12 UTC · 2 mo ago
took
9 min
linked to
NTT

Contracts were found and written: a token entity was created, or an existing one gained a contract or a route.

The record, as the feed sent it
feed id-662027617
transfer id—
status—
bridgeportal_bridge
sourcearbitrum · 0x8539e8da0b6f1616892a338ded4f2300bcff7da9
source tx0x55d0bd6b…b3b528
source block— · 2025-07-12 07:00:46 UTC
destinationbase · 0x8539e8da0b6f1616892a338ded4f2300bcff7da9
destination tx—
destination block— · —
token 0x9af6c42076cf1c54752cb628d6ce235e2d71814d open
symbol · name · decimalsNTT · NTT · 18
known asNTT · NTT · 0x9af6c42076cf1c54752cb628d6ce235e2d71814d learned from the transaction and the mint, not from the feed
amount sent · received— · —

raw payload

{
  "id": -662027617,
  "token": {
    "name": "NTT",
    "symbol": "NTT",
    "decimals": 18
  },
  "amount_sent": null,
  "bridge_slug": "portal_bridge",
  "token_address": "0x9af6c42076cf1c54752cb628d6ce235e2d71814d",
  "source_address": "0x8539e8da0b6f1616892a338ded4f2300bcff7da9",
  "source_log_index": 0,
  "source_chain_slug": "arbitrum",
  "destination_address": "0x8539e8da0b6f1616892a338ded4f2300bcff7da9",
  "destination_chain_slug": "base",
  "source_block_timestamp": 1752303646,
  "source_transaction_hash": "0x55d0bd6b2d068dfd4e89336b11e59f315f6d25906be9db4101bf399366b3b528"
}