Know your targets.
Rethink your channels.
Turn a pile of invoices into a clear view of destinations,
routing entry points, and the patterns in between.
Start with your invoices
No invoice-count cap. Decoding runs in a background worker. Your data stays in this tab and is never saved.
Your invoice landscape
Input quality
Explore over time
Amount distribution
Invoice counts by requested amount. Buckets are logarithmic, with lower bounds included.
Invoice anatomy
A quick read of routing, wallet markers, descriptions, and receiver identity.
Invoice expiry
Lifetime from creation, not payment timing.
Minimum final CLTV
Requested delta in blocks. Default: 18.
Real route hints
Alternatives per invoice, excluding Spark markers.
Capabilities & context
Read the results with confidence
Destination ≠ entry point
The destination is the n-tag key, or the key recovered from the signature. It may be private. With Spark, this is the Lightning service node—not the Spark wallet identity.
Alternatives ≠ payment volume
Each distinct real hint entry point gets one attribution per invoice. With no real hints, the destination is used. Multiple targets can receive the same amount attribution: don’t sum their amounts as volume.
Enrichment is opt-in
Only a manual lookup shares node public keys with mempool.space. Aliases and channel capacity describe today’s public network, not history or spendable liquidity. Unknown nodes aren’t necessarily private.