Public key

A public key is the shareable half of a crypto key pair, computed from the private key, and it lets anyone check that a transaction was signed by the holder of that private key without learning the private key itself. The private key signs and has to stay secret, while the public key, or an address made by hashing it, can be published.

The keys revealed in one block

When does a public key actually appear on a blockchain? For most bitcoin payments, at the moment the coins are spent. Block 975,527, mined at 06:47:35 UTC on November 12, 2026 and read in raw form from explorer mempool.space, shows how often.

Its 3,220 transactions spent 9,094 earlier outputs. In 5,928 of those inputs the spender published a 33-byte compressed public key beside the signature, because the coins sat at a SegWit address that holds only a 20-byte hash of the key. In one such transaction, the key beginning 03caaddc hashes to exactly the program inside the address bc1qhhdgkdjlpfvdnanclmcpmml55es4xe89k9gyy9, a check rerun for this entry.

Taproot works the other way round. Under BIP 341, the 32-byte program of a Taproot output represents a public key, so the key is visible from the day the coins arrive. The same block held 1,566 Taproot spends signed with the key alone, and of its 8,077 new outputs, 748 paid Taproot outputs while 5,546 paid the hashed SegWit kind.

Formats you will meet

The same key can be written in several ways, and the length usually tells you which one you are looking at.

Format Size Where it shows Source
Uncompressed 65 bytes, starting 0x04 Bitcoin Core before version 0.6 Bitcoin developer guide
Compressed 33 bytes, starting 0x02 or 0x03 Bitcoin spends from hashed addresses Bitcoin developer guide
X-only 32 bytes Inside every Taproot output BIP 341
Ethereum key Hashed with Keccak-256, last 20 bytes kept Only as a hash in the address ethereum.org

The Bitcoin guide says compressed keys lose no data and cut the block space a key needs almost in half, which is why they are the default in Bitcoin Core.

Public key vs private key

The US standards agency NIST, in its glossary, defines a public key as “the public part of an asymmetric key pair that is typically used to verify signatures or encrypt data.” The private key is the other part. Ethereum’s accounts page says the public key is generated from the private key and that you “cannot derive a private key from public keys.”

Why exposure may matter later

The gap between a hidden and a published key matters for one long-range risk. NIST’s draft transition plan, IR 8547, published on November 12, 2024, says ECDSA, the signature scheme the Bitcoin and Ethereum documentation describe for these keys, is “vulnerable to Shor’s Algorithm on a cryptographically relevant quantum computer.” Its table marks ECDSA “disallowed after 2035” at every security strength it lists.

The same document says no such computer exists yet that threatens current security levels. Still, a key already printed on-chain cannot be taken back.

The mistake: treating the key and the address as one

A common error is to assume your public key went public when you shared your address. For a hashed address it did not, and the block above shows it surfacing only at the first spend. A Taproot address, by contrast, publishes the key from the start. On Ethereum, ethereum.org adds, others can derive your public key from the signature on anything you sign, so the first outgoing transaction reveals it.

Where it comes up