In which sectors is blockchain used?

Blockchain is used or being tested in finance, supply chains, healthcare, public services, property, legal services, energy, media, retail, automotive and education. But those labels hide very different jobs. Moving a payment, checking a diploma and sharing a production report aren't the same application. The useful starting point for blockchain technology is which records need to be shared, and which independent parties need to check them.
A live service, a pilot and a research proposal are not interchangeable evidence. The sections below separate the intended use from its limits and date the documented examples. That's also the starting point for understanding how to use blockchain: adding a ledger doesn't automatically make an application cheaper, private or accurate. [1]
About the illustration: The mobile represents different industries using a shared-record approach. It is not a single network connecting every sector, or a claim that these systems operate in perfect balance.
1. Financial services: payments, settlement and asset records
Payments and cross-border transfers are about moving value and establishing an agreed transaction status. Whether a particular transfer is cheaper or faster depends on its fees, confirmation requirements and service arrangements. There is no universal low-cost or instant-payment guarantee. Keep Bitcoin and blockchain separate here: paying in BTC is one use of a particular network, not a requirement to move every financial record onto it. [2]
With asset tokenisation, a token represents a defined asset or right; the relationship between the token and that right still needs to be established. A documented test: the ECB's 4 December 2024 announcement described Eurosystem DLT settlement work carried out between May and November 2024. It distinguished trials using actual central bank money from experiments using mock settlement. That is evidence of testing, not evidence that banking as a whole has moved to blockchain. Scalability and total operating cost remain application-specific questions. [3] DLT is the broader distributed-ledger category; not every DLT design is a blockchain. [1]
2. Supply chains: following a product without confusing records with reality
A manufacturer, carrier, warehouse and buyer can contribute events to the history of the same batch: production, dispatch, receipt, inspection and acceptance. Supply-chain traceability brings those accounts together. It does not make the physical item trustworthy by definition. Imagine moving a genuine label onto a counterfeit component: a well-kept history won't automatically detect the swap. An intact record is not proof of an authentic product. The example shows why physical checks cannot simply disappear from the process.
The companies also need to agree on what their records mean. GS1 EPCIS defines a common way to exchange event information, with EPCIS 2.0 supporting sensor readings and certification data. It is a data-sharing standard, not a blockchain. Protocol standardisation, industrial communication and the ledger are different parts of the system. Connecting an Industrial IoT device doesn't, on its own, make every organisation interpret its data consistently. [4]
3. Healthcare: controlled access to records and pharmaceutical tracing
Keeping track of access to a medical record is different from publishing that record on a public chain. One possible design would retain documents in controlled storage and handle their hashes and authorised transaction records separately. That separates data integrity from data privacy. Fabric's private data collections provide one technical mechanism: authorised organisations share the data while its hash is recorded on the channel ledger. That capability alone does not establish that a healthcare application meets its requirements. [6]
Pharmaceutical tracing is a separate application. The FDA's DSCSA pilot programme lists the IBM/KPMG/Merck/Walmart blockchain interoperability pilot. It documents a trial in the pharmaceutical supply chain, not universal adoption or a blanket compliance guarantee. In a proposed cold-chain application, data-logger records would also depend on measurement accuracy and calibration. A ledger cannot replace the work needed to establish whether the recorded conditions were measured correctly. [5]
4. Public services: identities, credentials and voting
For identity and document checks, the questions include who issued a credential, whether its signature checks out and what authority the issuer had. The EBSI credential framework distinguishes issuers, holders and verifiers and connects their work to blockchain-based trust registries. This is not the same as putting everyone's personal details on a public ledger. EBSI's documented education work includes pilots, which should not be described as completed nationwide deployments. [7]
Voting has a different set of security requirements. The National Academies' 2018 report, Securing the Vote, explains that blockchain alone does not resolve malware on a voter's device, voter authorisation or ballot secrecy. A vote changed before it reaches the ledger is not repaired by keeping the resulting record unchanged. The report therefore distinguishes blockchain security from the end-to-end requirements of an election system. This is a technical assessment from a dated report, not a claim about the outcome of any election. [8]
5. Property: coordinating a transaction is not the same as transferring title
A property transaction involves several parties checking documents, signing agreements and completing payment steps. A shared workflow can help them see what has happened and who needs to act next. In its 24 May 2019 account of Digital Street, HM Land Registry described a Corda-based prototype using a copy of the Land Register. It was not a wholesale migration of the official register. The trial illustrates shared transaction visibility rather than the disappearance of the existing registration process. [9]
A token transfer and a legal transfer of property must be assessed separately. For a proposed system, ask what the token represents, which register is authoritative, who may authorise corrections and how disputes are handled. Calling the ledger immutable doesn't remove the need for corrections or transactions that reverse an earlier effect. These are project-design questions, not a determination of property law in any particular jurisdiction.
6. Legal services: executable rules and intellectual-property records
Smart-contract software carries out programmed operations; it does not necessarily contain an entire legally binding agreement. The Law Commission of England and Wales made that distinction in its 25 November 2021 work on smart legal contracts. In an industrial smart-contract workflow, code might update a job's status after an authorised acceptance statement. That doesn't mean the program settles every dispute or produces the same legal effect in every country. [10]
For intellectual property, a proposed system might associate file hashes, revisions and licence information. Yet creating a token linked to a work does not establish who owns the rights. WIPO's discussion of NFTs and copyright separates buying a token from acquiring copyright. A recorded ownership claim still needs to be distinguished from an established entitlement. The blockchain can preserve what someone asserted without deciding whether that assertion was valid. [11]
7. Energy: trading records, meter data and the physical grid
In peer-to-peer energy trading, a blockchain can support the commercial records associated with measured generation and consumption. An IRENA–SEDA session on 25 August 2020 covered lessons from Malaysia's Power Ledger-based trading pilot. That's a dated example of a trial, not evidence that consumers everywhere can sell power directly without restrictions. [12]
Recording a trade doesn't control where electricity flows. Energy-trading research considers settlement and delivery alongside grid constraints. A proposed system still needs to address meter data, connection limits and delivery responsibilities. Its performance cannot be reduced to transactions per second. Also keep the ledger's energy use separate from the carbon footprint of the generation it records: preserving a claim doesn't make the underlying electricity low-carbon. [20]
8. Media and entertainment: distribution, licences and royalties
A proposed content-distribution model could link usage reports, licence terms and revenue shares. But an automated payment isn't automatically a fair or complete payment. Suppose a reporting service omits some uses of a work. The code could distribute the resulting amount exactly as instructed and still underpay the creator. In that example, accurate usage reporting and the agreed revenue split are separate responsibilities from executing the payment.
Even an NFT royalty standard is not a universal collection mechanism. ERC-2981 communicates royalty information, including the recipient and amount, and describes royalty payments as voluntary. It does not force every later sale to pay the creator. That is a concrete limit behind some of the common misconceptions about blockchain and automated rights management. [13]
9. Retail and e-commerce: product histories, warranties and returns
A customer's product history might draw on manufacturer details, batch identifiers, dispatch and delivery events. GS1's event-sharing approach supplies a common language for exchanging that information. Choosing a blockchain doesn't mean showing the customer every commercial record: access and disclosure still need to be defined, including which details remain private between trading partners. [4] [6]
Consider a hypothetical spare-part sale. The parties could associate a serial number with a test report and warranty start date. A copied label, an unreported repair or a mistaken goods-receipt check would still need separate investigation. A return could be represented by a new record referring to the original sale rather than making that sale vanish. The potential benefit of blockchain here is agreement about accepted records, not a guarantee that every item and every business decision is correct.
10. Automotive: component compliance and vehicle histories
Part certificates, production batches and supplier declarations can be connected in a shared compliance workflow. Renault Group's 21 April 2021 XCEED announcement followed testing at Douai and described a partnership and rollout plans involving partner plants around Bursa, Douai and Palencia. It is a documented test and deployment announcement, not a statement that the entire automotive industry now uses the same system. [14]
For a proposed vehicle-history application, records might cover ownership, servicing, replacement parts and reported accidents. An accident nobody reports won't appear simply because the database uses blockchain. A digital twin could relate these records to a model of the vehicle, while the ledger supports selected shared records. Those are different jobs, not two names for the same technology. The wider Industry 4.0 integration needs to assign responsibility for recording events as well as moving the data.
11. Education: checking diplomas and professional credentials
Digital diplomas provide a documented example. MIT's 2017 pilot associated verification evidence with the Bitcoin blockchain rather than placing the complete diploma file on it. MIT's verification guidance explains how a certificate URL or JSON file can be used to check the credential and its issuer. Keeping the document and checking whether it has changed are separate tasks. [15]
Not every digital credential needs a blockchain. The W3C Verifiable Credentials model allows several types of registry, including trusted databases and distributed ledgers. It also distinguishes checking a credential's cryptographic evidence from establishing that every claim inside it is true. When assessing a professional certificate, the receiving organisation still needs to consider the issuer and its own acceptance rules. That distinction also matters for standards and qualification documentation. [16]
Manufacturing and automation: following a heat-treatment batch
Manufacturing-data traceability research reported by NIST in 2019 explored blockchain-based records for manufacturing files and process history. The heat-treatment workflow here is a separate hypothetical example. Imagine a component maker, a heat-treatment subcontractor and a customer trying to agree on which batch was processed and which report supported its acceptance. Their problem is manufacturing data integrity, not how to control a furnace through a blockchain. [17]
In this design, the batch ID, recipe revision, timestamps, temperature trace and authorised acceptance statement would be associated with one another. Temperature measurement remains its own engineering task. The recording system keeps the raw readings; an edge application prepares the report and submits its hash. The document itself can stay in controlled cloud storage or on an internal server. Data analytics can look for deviations in the trace, while comparing hashes helps determine whether a later report copy has changed. This is one possible arrangement, not a requirement to record every sensor sample on-chain.
Keep control separate from record approval. NIST's operational-technology security guide treats security alongside performance, reliability and safety. In this example, the furnace's control and safety functions would not wait for a remote ledger approval. Real-time monitoring, industrial cybersecurity and document verification have different roles. Preserving a bad measurement does not turn it into a good one. [18]
A use case is not a reason to put every project on blockchain
Discontinued projects belong in the picture too. On 29 November 2022, Maersk and IBM announced that TradeLens would be discontinued. Maersk cited insufficient industry collaboration and commercial viability, with shutdown intended by the end of Q1 2023. The case illustrates a distinction worth keeping: a technically viable platform is not necessarily a sustainable shared business. [19]
For a design review, start with the participants. Do independent organisations need to create and check the same records? Why isn't one party's database acceptable? Who corrects mistakes, and what happens when a key is lost or a required participant becomes unavailable? Implementation challenges and blockchain's limitations become much clearer when those questions are answered. If signed documents, an access-controlled database and audit logs already meet the need, the additional network needs a specific justification.
The industry changes; the underlying questions often don't. Who recorded what, under which authority, and how can another party check it? Blockchain can provide part of that record-keeping infrastructure. It does not, by name alone, establish physical authenticity, measurement quality, legal effect or a workable business model.