Loop Tracker

This page identifies all plausible Loop redeems or recoveries detected on-chain, given they have a custom known script. List will be updated every hour at most.

Learn more about Loop by Lightning Labs, also read their article Loop Out In-depth.

Legend

Redeem Hash Lock A successful Loop transaction, where the end node reveals the Hash Lock pre-image that can be used to settle the invoice paid off-chain.
Recover Time Lock An unsuccessful Loop transaction, where the Loop server recover their on-chain funds after the end node did not reveal the Hash Lock pre-image. Invoice off-chain was not settled.
At this moment Loop uses two kinds of HTLC versions. v2 was introduced live with loop v0.9.0-beta, but shipped even before that. v1 was the original script since mainnet launch. You can further differentiate these versions via the nSequence field, as v1 sets it to 0 and v2 to 1.

Hashes are specified in OP_HASH160 format when they are not revealed, specifically RIPEMD-160(SHA-256(pre-image)). Otherwise if revealed they are specified in OP_SHA256, specifically SHA-256(pre-image) for ease of search.
You can save your node forward hash locks and correlate their values here (base64-encoded).
Transactions listed here are a guess. Anyone could create similar-looking transactions (for example, Boltz is known to use v1-looking HTLCs). Inspect input transactions to find known 2-of-2 multisig channel closures against LOOP node to have a better assurance.
Some transactions have been removed due to signalling of not being part of Loop.

But I thought Lightning Network / Loop was private and secure?

Lightning Network / Loop service IS private. There is no information that allows you to see who wanted to Loop Out / In, the most that could be done is use the hash lock information to trace a specific payment through the Lightning Network, and even then you don't know if it is a forward or not.
The security of the transaction is not affected. This is just collecting all the publicly available information from on-chain and listing it in one single place.
With the Taproot/MAST upcoming upgrade, the ability to identify Loop-style transactions by script alone would be reduced, as after confirmation the node and Loop could agree off-chain to reveal the pre-image, then take a different Merkle tree path that just looks like a 2-of-2 multisig.
This improvement is not written yet, but should be fairly easy to achieve. Do note there are other ways to guess if a transaction is Loop or not, but it should prevent direct simple lookups.

Like this? Open a channel towards ln.LightningHoarder.net, or send some satoshis via channel push / KeySend / bc1q49f6p2j3hc7yheq7kfuvdyl5hgavx8x79230lq4js2ktdxaws80shx35mn

---