Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with segwit2x
Search options not deleted
user 21496
SegWit2X was a failed hard fork attempt designed to increase the block size limit.
6
votes
What was the number of the block in which SegWit got activated? And first transaction?
This is a very old question but probably someone else needs to know the same:
SegWit was activated in block 481824 and that block has two p2wpkh txs:
dfcec48bb8491856c353306ab5febeb7e99e4d783eedf3de …
- 201