TI
ethereum →
binance
Pin #9629
receivedqueueddiscovered · 2 h 39 min
- token
- TIMEChronoTech Token
- bridge
deBridge
- token entity
- TIMEits contracts and routes
- bridge tx
- 0x8792d953…20c9edon ethereum
- delivery tx
- —on binance
What happened to this pin
pin received
2026-09-06 14:06:19 UTC · 2 mo ago · #9629 from the feed
accepted by ingest
2026-09-06 14:06:19 UTC · 2 mo ago · priority high
discovery outcome
2026-09-06 16:45:02 UTC · 2 mo ago · DISCOVERED after 2 h 39 min
token
TIME — its contracts, routes and alerts are on its own page
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 | -1716210256 |
| transfer id | — |
| status | — |
| bridge | debridge |
| source | ethereum · 0x4b1bb2f16721ad266e5c9e83e34608c41e15954a |
| source tx | 0x8792d953…20c9ed |
| source block | — · 2026-04-29 20:39:11 UTC |
| destination | binance · 0x4b1bb2f16721ad266e5c9e83e34608c41e15954a |
| destination tx | — |
| destination block | — · — |
| token |
0x3f44d40186f477c52024932c46fd425221a16f9c
open
|
| symbol · name · decimals | TIME · ChronoTech Token · 8 |
| known as | TIME · ChronoTech Token · 0x3f44d40186f477c52024932c46fd425221a16f9c learned from the transaction and the mint, not from the feed |
| amount sent · received | — · — |
raw payload
{
"id": -1716210256,
"token": {
"name": "ChronoTech Token",
"symbol": "TIME",
"decimals": 8
},
"amount_sent": null,
"bridge_slug": "debridge",
"token_address": "0x3f44d40186f477c52024932c46fd425221a16f9c",
"source_address": "0x4b1bb2f16721ad266e5c9e83e34608c41e15954a",
"source_log_index": 0,
"source_chain_slug": "ethereum",
"destination_address": "0x4b1bb2f16721ad266e5c9e83e34608c41e15954a",
"destination_chain_slug": "binance",
"source_block_timestamp": 1777495151,
"source_transaction_hash": "0x8792d95398b42760d736cea80f2fa3ef9726f68b02fb38ed84ef589c4920c9ed"
}