This goes above my head... Does this mean someone created an input that's impossible to spend this century?
Take the locking script OP shared above:
483045022100a688c15bad1efdadf609c898421cca929da4c2f27fc97fc3dce018228c81460c02203f876bb82dcdd6cdddf36f44f14df38904759ee8d163b69800fffd0665ee292e014903a0f26cb17541045332b5e3bcaeef3a062b49d5129ac21017d369e9c52c2f12c472d8d6236e2f5116b580dd1f99fd9b321d9207c9a512f301c263bd58238dbbebf469675e09a2b2ac
Breaking that down, we get the following:
48 - Push 72 bytes to the stack
30 - Header byte indicating signature
45 - Length of what follows (69 bytes)
02 - Header byte for R
21 - Length of R (33 bytes)
00a6....1460c - R
02 - Header byte for S
20 - Length of S (32 bytes)
3f87....2e01 - S
--------------------------------
49 - Push 73 bytes to the stack
03 - Push 3 bytes to the stack
a0f26c - Little endian encoding of 7,140,000
b1 - OP_CHECKLOCKTIMEVERIFY
75 - OP_DROP
41 - Push 66 bytes to the stack
0453....a2b2 - Uncompressed public key
ac - OP_CHECKSIG
If we haven't hit the necessary block as specified, then the script terminates in an error. If we have reached the necessary block, then OP_CHECKLOCKTIMEVERIFY will verify, OP_DROP will clear the stack, and then all that is left will be the pubkey and OP_CHECKSIG as it would be in a old school P2PK output.