BlockQuery powered by Chainlabs.ai

Answers  /  4 September 2026

Can you see who sent a Bitcoin transaction before it confirms?

Yes, for the entities BlockQuery has attributed. A Bitcoin transaction is visible in the mempool before it is included in a block, and if the sending address belongs to an attributed entity the sender can be named at that point: a specific desk or treasury moving size before it lands on-chain. BlockQuery's Bitcoin coverage runs to 312M+ attributed addresses.

Published 4 September 2026 · BlockQuery, powered by Chainlabs

312M+
Bitcoin addresses attributed
800+
OTC desks
90,000
directly researched addresses
30+
blockchains

What the mempool shows

A broadcast transaction waits in the mempool until a miner includes it in a block. During that window it is public: inputs, outputs and amount. What it does not show is who is behind the inputs.

Where attribution comes in

If an input address belongs to an attributed entity, the transaction can be read as that entity sending that amount while it is still unconfirmed. This is the same entity attribution applied earlier in the transaction's life, not a different dataset.

What it is not

It is not a promise of sub-second delivery, and it is not a prediction of what the transaction means for price. It is an attributed transaction, earlier. What you do with the time is yours.

How it is delivered

As an optional mempool feed in the same schema as the confirmed-history feed, so a model built on history runs unchanged on unconfirmed transactions. Available with the entity data feeds.

Frequently asked questions

Can a transaction change before it confirms?

Yes. Bitcoin allows a transaction to be replaced with a higher fee, and an unconfirmed transaction can be dropped. A mempool record is a record of intent at broadcast; the confirmed feed is the record of what happened.

Does this work for Ethereum or Tron?

The mempool feed is Bitcoin first. Additional chains are available on request rather than promised as live.

How far ahead of confirmation is it?

Until a miner includes the transaction in a block, which varies with fees and network load. BlockQuery does not claim a fixed latency.

Do you name the receiving side as well?

Where the destination address is attributed, yes. Both sides are named where we have them.

Request one month of sample data

Entity data feeds: the attribution layer as data you own, in the schema you would receive.

Request one month of sample data