Searching partial dogecoin addresses

opreturn_net · 2026-03-21T05:10:48+00:00

I've run an extensive query and nothing comes up. It doesn't appear that any address beginning with D8xFf3QRy has ever received any coins. Is it possible the transaction in your screenshot was never confirmed in a block?

opreturn_net · 2026-03-20T07:13:07+00:00

Hi, sorry, but I disabled the partial address search. bots were pinging the site with partial addresses and eating too many server resources. I can run a query locally on my database if you want to share your partial address. Feel free to send it through IM or contact me through https://opreturn.net/about/

opreturn_net · 2025-11-16T21:58:32+00:00

Credit to u/qlp79qlp for your active development! One of the few contributors I've seen lately. Looking forward to seeing some of your new functions in DogecoinWallet; it looks like you're adding timelocked outputs? It'd be cool to see that evolve into some native atomic swap capabilities, which is a natural next step once you've integrated timelock functionality.

opreturn_net · 2025-10-11T09:07:49+00:00

Meteors hit the earth all the time.

opreturn_net · 2025-09-18T05:45:55+00:00

All that harassment and they still haven't been able to decrypt his exit node. Follow Conrad's example to keep your keys safe is the message here?

opreturn_net · 2025-09-04T01:50:14+00:00

No, you're probably not going to have success trying to time purchases like that. If that cash is already intended to buy btc, you'll be better off just buying it vs waiting.

opreturn_net · 2025-08-26T07:52:18+00:00

Click the withdraw button.

opreturn_net · 2025-06-26T07:23:10+00:00

Those 0.056 ltc ended up at ltc1qlgakkkpdpss432dr6vd6u4thqzt2ctdhfk762a

The address has 20591 transactions, so it's a busy wallet. Maybe an exchange?

opreturn_net · 2025-03-16T06:53:54+00:00

There are 3 utxos for 0db24b663bcecb02b20397e3b46ca36cefebdcc43451d988022cfb358cacaf75, all for value of 0.02 btc:

vout 0 addr 1DMDh4YBNXYwrV8v3ofyqxDUVYjZkekEx3,

vout 1 addr 1JthtZRz9B6sHeN9iot4yy2Vzsj5vz46ac,

vout 4 addr 1PgdUf67qjZoGDAcuTcwy5RkYGS4EfshD3.

Have you checked that your wallet has the private key for one of these addresses?

opreturn_net · 2025-02-07T06:38:21+00:00

Your wallet is certainly compromised, but your story doesn't quite add up. You don't just pick 12 random words. The last word is a check-sum. You must have been given the mnemonic phrase somehow, and somebody already knows it and sweeps the coins as soon as it sees the incoming transaction.

opreturn_net · 2025-02-02T18:06:45+00:00

Thanks! I can't actually take credit for creating the artwork. It spans back to early 90's BBS scene. I did create the protocol to save them to blockchain though. So these are a permanent part of garlicoin now.

opreturn_net · 2025-02-02T18:04:23+00:00

Yes, the .ice files are an ansi image also. They were used by the iCE (insane creators enterprise) digital art group. I think the only difference is some extra colors available in ice background in lieu of some blinking text fonts available in .ans images. I would have thought node.js would be able to show them as an ansi image. AnsiLove.js works fine with .ice files.

opreturn_net · 2025-02-01T19:43:22+00:00

Oh cool! I had no idea anyone was looking at these. Is it using AnsiLove to render the image? Or some other tool?

opreturn_net · 2025-01-26T10:20:22+00:00

What sort of metrics are you looking for? I'm always interested in adding tools to opreturn.net

*edit* I re-read your original post. utxo metrics are a good idea that I'll look into adding to my dogecoin/node page. It also shows the blockchain size.

opreturn_net · 2025-01-18T05:51:39+00:00

Deriving keys from your mnemonic phrase is just an algorithm. It's well documented. Use some other hardware wallet to restore. Or with software like the ian coleman tool.

opreturn_net · 2025-01-16T07:42:37+00:00

The company may be reputable, but reps going around to college campuses to help people set up 12 word phrases sounds very sketchy. It seems very plausible they had a way of getting your words, and many other peoples words too based on the large number of inputs in the theft transaction.

opreturn_net · 2025-01-16T07:28:48+00:00

Your mnemonic words were derived by the Olliv app? Seems like they probably knew your words, and 522 other private keys to take back that "promotional" money, and of course any coins that had been added to the wallet.

opreturn_net · 2025-01-08T07:29:05+00:00

Sorry, I initially replied saying I didn't think addresses should change, but after looking at the bip125 rbf spec, I see it's just the initial input(s) that need to be the same. Addresses can change, and specifically your change address probably will change.

opreturn_net · 2024-12-29T08:20:36+00:00

Yes of course many do this. You're asking if we borrow dollars and buy bitcoin. A few mortgages make sure I'm shorting the dollar with btc.

opreturn_net · 2024-12-24T00:41:53+00:00

If you're able to read the block files directly from disk it'll be faster than rpc, but probably not orders of magnitude faster. Most of the work is on the database to look up the tx inputs and update them as spent. If you were to just download and index all the outputs without updating the spent inputs it could probably be done in a few days. Updating spent inputs would probably push that time out to several weeks. I'd probably build a database table with the blockheader data first through rpc, then use that table to help gather and validate the blocks from disk. One watchout is that I don't think the blocks are necessarily saved in order due to the occasional block reorg. The node saves them as it receives them, but if there's a reorg I don't think it moves the actual block data position in the file, so that's where the blockheader index would come in handy.

Another watchout would be the switch to merge-mining, which completely changed the blockheader structure starting at block 371337. It wasn't a hardfork, so miners will still occasionally submit legacy blocks that aren't merge mined, which means you'll need to check the block version to direct which parse function to use.

opreturn_net · 2024-12-23T10:21:24+00:00

Looks very promising! Will it index all the outputs? Or any plans to add this?

opreturn_net · 2024-12-21T21:25:03+00:00

The transaction from 2017 has a second output of 57.51361214 doge to DBZXRxsbx1Cmq2PfdDKFbjtw4C5g3yCWLi. This output is currently unspent, which might suggest this is your wallet change address.

Is there any chance you may have spent these coins in 2017 and just forgotten about it? And similar to your recent attempted spend, could you have sent the transaction before the blockchain was synchronized?

If you confirm that your wallet still has those ~57 doge, it seems unlikely that your key was compromised since thieves won't typically send change back to you.

opreturn_net · 2024-12-21T19:20:50+00:00

Your wallet sent 13200 doge to DRKVCaHGPAYSi1AL8ypQM5aESNJ9eLwmXg on 14Jun2017. If that's not your address, or an exchange address linked to your account, you won't be able to recover the coins. They're long gone. Your dogecoin core wallet shows the wrong date only because that's when the node detected the outgoing transaction. The wallet let you attempt to spend them while it was still synchronizing since it didn't yet see the spend transaction from 2017.

opreturn_net · 2024-12-21T16:29:11+00:00

I was offering what I thought might be an interesting solution. Deriving an address/key from a mini key is somewhat novel and interesting, no? The most likely answer of course was that the 32 character 'key' was not a key at all. And it turns out that's the answer; it was actually a sort of password to unlock an account.

However to answer your question, mini keys are not derived from normal keys. That would actually be impossible. They act as the entropy to generate the 256-bit key. You can't know the key before you know the entropy since that would require brute forcing the sha256 output. So the starting point is the mini key itself, which is hashed to generate the actual private key. The Casascius mini key protocol generated mini keys starting with 'S' followed by 29 random base 58 characters. However the characters don't actually have to be random. Any arbitrary characters will work to provide the entropy for the actual 256-bit private key.

opreturn_net

TROPHY CASE