Asset
TCOM · BNB Chain pool
Trip.com Group (Ondo Tokenized)
Verified
Last confirmed 20 Oct 2026, 10:15 UTCNext check ~20 Oct 2026, 16:15 UTC – 21 Oct 2026, 10:15 UTC (6–24 h cadence)
- Chain
- BNB Chain
- Kind
- Pool
- Venue
- pancake-v2
- Pair
- CN6900 / TCOMon
- First seen
- 20 Oct 2026, 10:15 UTC
- Observations
- 1
- Last attempt
- 20 Oct 2026, 10:15 UTC
- Base token
- CN6900 · 0x3808…7777
- Quote token
- TCOMon · 0x6459…6969 ✓
- Address
0x540eeb5c4ced0b390f0df03b85b5b03ffd97e74e0x540e…e74e
Last-confirmed read status, not a safety rating. Next check is approximate; normal cadence is unchanged.
Observations
Check history
● Match
Observation details · 1 records
| Time (UTC) | Asset / facet | Observation | Evidence |
|---|---|---|---|
| BNB Chain 0x540e…e74e Contract match | Verified | block 128728468 Record ↗ |
How to read this history
Verified means an issuer-published contract match, not safety, backing or custody. Controls observed is a controls read, not an identity verdict. One or two missed scheduled slots retain the last confirmed result; three show Unverified. A due attempt blocked by QED's daily budget counts once per UTC hour without provider access. On-demand misses and rejected on-demand requests never advance that counter. Registry changes and unsupported venues are not RPC misses. Partial controls remain visible. Last confirmed never extends a signed record’s expiry.
Public, wallet-free attempts and their outcomes appear here. Cache hits and page render deadlines add no observation. Missing historical reads cannot be reconstructed. CSV and JSON exports are paginated operational history, not signed attestations.