Use the search bar at the top of the website to search for a specific transaction.

Or you could just check out a random one:

Random Mempool Transaction
Random Blockchain Transaction

Examples

Basic

P2PKH
P2MS
P2SH
P2MS
P2SH
P2WPKH
  • 8b8d1473ce0a9936b70524435d37d37ae226d39f74ce8ff7abf545c501dfce9e (13 Jul 2023)
  • This transaction contains a single P2WPKH output. They work in a similar way to P2PKH in that you lock the output to a public key, but they use the witness field instead of the scriptsig field for unlocking. These are now used in favour of the legacy P2PKH locking scripts.
P2WSH
P2TR

Technical

Coinbase Transaction
  • a8d0c0184dde994a09ec054286f1ce581bebf46446a512166eae7628734ea0a5 (25 Feb 2016)
  • A coinbase transaction is a special as it doesn't "spend" any previous outputs. Therefore, for the input to the transaction the "previous TXID" is all zeros. The input scriptsig is also redundant, so miners typically use it for inserting custom text and data.
Coinbase Transaction (Segwit)
Relative Locktime

Interesting

SHA-1 Hash Collision Spend
  • 8d31992805518fd62daa3bdd2a5c4fd2cd3054c9b3dca1d78055e9528cff6adc (23 Feb 2017)
  • This transaction spends the Peter Todd SHA-1 hash collision locking script. Basically, the original transaction contained a P2SH output with custom script inside. If you look at the spending transaction you can see that the redeem script was 6e879169a77ca787, which as opcodes is: OP_2DUP OP_EQUAL OP_NOT OP_VERIFY OP_SHA1 OP_SWAP OP_SHA1 OP_EQUAL. In other words, to spend this output, you needed to find two different pieces of data that hash to the same value when using SHA-1. The original 1 BTC bounty output lock was created on 13 Sep 2013, and it was finally spent on 23 Feb 2017 (shortly after SHA-1 hash collisions were first found).

Famous

Pizza Transaction
  • a1075db55d416d3ca199f55b6084e2115b9345e16c5cf302fc80e9d5fbf5d48d (22 May 2010)
  • This is the famous 10,000 BTC Pizza transaction made by Laszlo back in May 2010. It's significant because it was the first time bitcoin was ever used to purchase real-world goods, which gave bitcoins real-world value (as opposed to just being a valueless digital currency). People today sometimes joke about how he paid 10,000 BTC for a pizza considering today's exchange rate, but Laszlo effectively created the exchange rate for bitcoin, which makes him (and this transaction) an important part of bitcoin's history. Thanks Laszlo.

Firsts

P2PK
  • f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16 (12 Jan 2009)
  • These P2PK outputs were used in the early days of bitcoin (primarily by miners in coinbase transactions), but are rarely used anymore. This was the first ever "actual" bitcoin transaction (i.e. not a coinbase transaction) sent by Satoshi to Hal Finney.
P2PKH
P2MS
P2SH
OP_RETURN
  • 1a2e22a717d626fc5db363582007c46924ae6b28319f07cb1b907776bd8293fc (29 Mar 2013)
  • This was the first transaction that used OP_RETURN to store a string of ASCII text inside an output. The data push after the OP_RETURN opcode contains the string: "!Twenty byte digest.". This effectively burned the 0.05000000 BTC that was used as an input (worth $4.50 at the time), as OP_RETURN outputs cannot be spent and there was no other output created to send the coins onwards.
P2WPKH
P2WSH

Largest

Some of these transactions contain a large amount of data. Opening them on this blockchain explorer may cause your browser to crash.

Size
Size (1 MB Block Limit)
Number of inputs
  • 52539a56b1eb890504b775171923430f0355eb836a57134ba598170a2f8980c1 (01 Aug 2015)
  • This transaction spends 20,000 inputs. This is not the only one though, as were nine 20,000-input transactions made on the same day 01 Aug 2015, presumably by the same person. I'm not sure why, but I'd guess it was part of some sort of test.
Number of outputs
Fee
  • cc455ae816e6cdafdb58d54e35d4f46d860047458eacf1c7405dc634631c570d (26 Apr 2016)
  • This transaction has a fee of 291.2409 BTC ($135,770.68 at the time). This is because it spends 13 outputs with a total value of 291.241 BTC but only creates 1 output with a value of 0.0001 BTC, which meant the remainder could be collected as the transaction fee by the miner. Transactions with fees this large are usually created by mistake, and this is a particularly bad mistake.
  • Note: The block explorer on this site doesn't show transaction fees. This is because it gets transaction data using bitcoin-cli getrawtransaction only, and fees are not given for mined transactions. You can look up inputs manually to see their values, but I purposely don't do this to reduce the number of queries I need to make and to keep the pages as fast as possible.
scriptpubkey