Documentation Index
Fetch the complete documentation index at: https://mintlify.com/mempool/mempool/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The Lightning Explorer provides deep insights into Bitcoin’s Lightning Network - a Layer 2 payment protocol enabling instant, low-fee transactions. Explore nodes, channels, capacity statistics, and network topology.What is Lightning Network?
The Lightning Network is a second-layer protocol built on top of Bitcoin:- Instant Payments: Transactions confirm immediately
- Low Fees: Typically < 1 sat per transaction
- Scalability: Millions of transactions per second possible
- Privacy: Payments don’t appear on the blockchain
Lightning uses payment channels - pre-funded connections between nodes that allow multiple transactions without touching the blockchain.
Key Features
Node Explorer
Search and analyze Lightning nodes including capacity, channels, and connectivity.
Channel Analytics
View channel details, fees, capacity, and routing statistics.
Network Statistics
Track total capacity, node count, channel count, and growth metrics.
Topology Map
Visualize network structure and node connections.
Network Statistics
Global Metrics
The dashboard displays key Lightning Network stats:- Network Capacity
- Node Count
- Channel Count
- Growth Trends
Total BTC LockedSum of all Bitcoin locked in Lightning channels:
- Total capacity in BTC and USD
- Growth over time
- Percentage of Bitcoin supply
- Comparison to historical peaks
Network Health
Indicators of Lightning Network health:Average Channel Size
Median: ~5,000,000 sats (0.05 BTC)Larger channels support bigger payments
Connectivity
Average channels per node: 5-10Higher connectivity = better routing
Well-Connected Nodes
Top nodes with 100+ channelsHub nodes improve payment reliability
Channel Updates
Fee and capacity changes indicate active management
Node Explorer
Finding Nodes
Search for Lightning nodes by:- Node public key: 66-character hex string
- Node alias: Human-readable name
- IP address or Tor address
Node Details
When viewing a node, see:- Overview
- Capacity
- Channels
- Statistics
Node Information
- Alias: Node’s chosen name
- Public Key: Unique identifier
- Color: Display color (cosmetic)
- Network Address: IP or Tor onion
- Implementation: Software (LND, CLN, Eclair, etc.)
- First Seen: When node joined network
- Last Update: Most recent activity
Top Nodes Ranking
View the largest and most connected nodes:- By Capacity
- By Channels
- By Age
Nodes ranked by total BTC capacity:
- Major exchanges (Kraken, Bitfinex)
- Large routing nodes
- Payment processors
- Infrastructure providers
Channel Explorer
Channel Components
Each Lightning channel has:- Two participants: Nodes at each end
- Capacity: Total BTC locked in channel
- Balance distribution: How capacity is split (private)
- Routing policies: Fees charged by each side
- Channel ID: Unique identifier
- Funding transaction: On-chain tx that opened channel
Channel Details
- Basic Info
- Routing Policies
- On-Chain Data
- Historical Data
Channel Overview
- Channel ID: Unique identifier
- Node 1 & Node 2: Connected nodes
- Capacity: Total channel size
- Status: Active, inactive, or closed
- Age: Time since channel opened
- Last Update: Recent fee/policy changes
Channel States
Active
Channel is online and routing payments
Inactive
One or both nodes offline
Closed
Channel has been closed (cooperatively or forced)
Network Topology
Visualization
Interactive network graph showing:- Nodes: Represented as circles
- Channels: Lines connecting nodes
- Size: Indicates capacity or connectivity
- Color: Can represent age, fees, or status
- Clusters: Groups of well-connected nodes
Network Structure
Lightning exhibits “small-world” properties:- Hub-and-spoke: Large nodes connect many smaller ones
- Short paths: Most payments route through 3-5 hops
- Clustering: Regional or business-related groups
- Scale-free: Power-law distribution of connections
The network’s structure naturally emerges from economic incentives - hubs earn routing fees, so liquidity flows to well-connected nodes.
Payment Routing
How Lightning Payments Work
Routing Analysis
The explorer shows routing metrics:- Path length distribution: How many hops payments take
- Success rates: Percentage of successful payments
- Common routes: Most-used paths through network
- Bottlenecks: Channels limiting payment capacity
Node Operations
Running a Lightning Node
Considerations for node operators:Liquidity Management
Balance inbound/outbound capacity for optimal routing
Channel Partners
Choose well-connected, reliable nodes
Fee Optimization
Set competitive fees to attract routing
Monitoring
Track performance and rebalance channels
Best Practices
Open channels to diverse, well-connected nodes
Monitor channel balance and rebalance regularly
Keep node online for reliability
Update software and monitor security
Start small and scale as you learn
Consider automation for channel management
Lightning Statistics
Historical Metrics
Track network evolution:- Capacity Growth
- Node Adoption
- Channel Dynamics
- Usage Metrics
Total BTC locked over time:
- Launch to present trajectory
- Major milestones (1000 BTC, 5000 BTC, etc.)
- Impact of market conditions
- Correlation with Bitcoin price
Comparative Analysis
vs. On-Chain
Lightning advantages:
- 100,000x faster
- 1,000x cheaper
- Better privacy
- Instant finality
vs. Other L2s
Lightning specifics:
- Trustless (cryptographic)
- Bitcoin-native
- Mature ecosystem
- Production-ready
Use Cases
What Lightning Enables
- Micropayments
- Instant Payments
- Frequent Payments
- Cross-Border
Payments Too Small for On-Chain
- Streaming sats per second
- Pay-per-article content
- Gaming and tipping
- IoT machine-to-machine payments
Lightning Wallets
Popular Lightning-enabled wallets:Phoenix
Mobile wallet by ACINQ with automatic channel management
Breez
Self-custodial mobile wallet with podcast app
Zeus
Mobile interface for LND/CLN nodes
Muun
Hybrid on-chain/Lightning wallet
BlueWallet
Bitcoin and Lightning wallet
Wallet of Satoshi
Custodial Lightning wallet (easiest for beginners)
API Access
Query Lightning Network data:Privacy Considerations
Lightning Privacy Features
Onion Routing
Payment paths encrypted, intermediate nodes don’t know sender/receiver
No Blockchain Records
Payments don’t appear on public blockchain
Private Channels
Channels can be unannounced for extra privacy
Blinded Paths
Recipients can hide their node identity
Privacy Limitations
Troubleshooting
Why did my payment fail?
Why did my payment fail?
Common reasons:
- Insufficient liquidity in route
- Channel partner offline
- Fee too low for route
- Payment amount too large
- No path found to recipient
Why can't I receive payments?
Why can't I receive payments?
Need inbound liquidity:
- Open channels (provides outbound)
- Have others open to you (inbound)
- Use submarine swaps
- Request inbound from LSP
Why are channels closing?
Why are channels closing?
Channels close when:
- Either party closes cooperatively
- Force close due to dispute
- Breach remedy (cheating attempt)
- Node goes offline too long
Why is capacity decreasing?
Why is capacity decreasing?
Network capacity changes due to:
- Channels closing (removes capacity)
- Price volatility (BTC value changes)
- Node operators adjusting positions
- Normal market dynamics
Future Developments
Upcoming Features
Taproot Channels
More privacy and efficiency with MuSig2
Channel Factories
Shared UTXO for multiple channels
Eltoo
Simplified channel updates
Trampoline Routing
Let others handle routing complexity
Dual-Funded Channels
Both parties contribute to channel
Splicing
Add/remove funds without closing
Related Features
Blockchain Explorer
View on-chain channel opening/closing transactions
Mempool Visualizer
See on-chain fees Lightning helps you avoid
Fee Estimation
Compare Lightning vs. on-chain costs
Mining Dashboard
Understand Layer 1 that secures Lightning