Before you open, see the evidence.
A concise prospective-peer view for operators considering a channel. Start with the node's public posture, then inspect historical signals and reachability through its existing channels.
Snapshot needs a refresh
A public snapshot exists, but refresh its evidence before relying on it.
Node posture and public indicators
Compact context for deciding what to investigate next.
Advertised capacity
Visible channels
Score confidence
Fee posture
Advertised fee observations associated with the assessed node's public channels.
Historical signals
Prepared comparison signals where sufficient history exists.
Fee-profile trend is shown using the prepared product's semantic label; it is not presented as a claim that actual node fees rose or fell.
Reachability through existing channels
How effectively does this node's current channel set demonstrate public route reachability?
Each row is a public channel observed in the prepared evidence. The four directions describe route construction through the assessed node and its connected peer. Select deeper analysis to see observed amount and coverage detail.
| Existing peer | Capacity | Direct node → peer | Direct peer → node | Outbound from node | Inbound to node |
|---|---|---|---|---|---|
| 🌟Star⭐️Service🌟0355157b...e52488e3Channel 1028571137643839489 | 40,000 | Mixed resultsMixed results |
No routes observedNo routes observed |
Mixed resultsMixed results |
No routes observedNo routes observed |
Point-in-time public Lightning graph route construction.
Deeper observed-amount analysis
See the amount ranges and direction-specific evidence already present in this snapshot. Viewing this does not trigger a new analysis or probe.
Observed ranges are point-in-time public routing evidence under the tested conditions. They are not channel liquidity, channel balance or guaranteed forwarding capacity.
Glossary
Definitions for the reachability evidence shown above.
- Direct Node → Peer
- Can a public route cross this specific channel from the node to a peer?
- Direct Peer → Node
- Can a public route cross this specific channel from the peer back to the node?
- Outbound From Node
- Can this channel act as the first step in routes from the node onward to the tested destinations?
- Inbound To Node
- Can this channel act as the final step in routes from the tested destinations back to the node?
- Route observations
- Public route results observed during the prepared tests. Routes observed means a route was constructed; Mixed results means results were not consistent across the tested conditions; Insufficient evidence means the evidence was not enough to assess the direction.
- Route-construction coverage
- The proportion of tested route constructions that produced a result, for example 1/1 (100%).
- Destination coverage
- The proportion of tested destinations for which a route result was observed, for example 1/1 (100%).
- Observed amount
- The payment amount used in a public routing test or the highest amount observed to route. It is not private liquidity, a channel balance or guaranteed forwarding capacity.
Inspect another public node
Paste a compressed node public key to request the same bounded view.