questions about OP Stack re-orgs:
- can unsafe blocks be re-orged by the sequencer?
- if so, how often are unsafe blocks re-orged?
- in practice how many confirmations before block become safe?
- is there a way to view historical re-orgs?
- (bonus) what's the best way to detect a re-oreg?

Related to safe, you can see the data in seconds here by chain:

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

Related to safe, you can see the data in seconds here by chain: 

https://dune.com/oplabspbc/op-stack-chains-l1-activity#submission-frequency

Contributing to OP Labs. Come join me on the track if you’re in /austin @ atxsprint.club

data @ op labs, building @optimism 🔴✨ | go /gators 🐊  | casts are my own things | msilb7.com

paging @msilb7 

One on the left is the one you want for the current discussion. Cant opine about one on the right

omg what an old dashboard.

Left: Time between BatchInbox transactions (these are the blob-carrying transactions that post batches of L2 transactions to L1) https://specs.optimism.io/glossary.html?highlight=batcher#batcher

Right: Time between State Output Proposals (aka Dispute Games, these are the L2s posting the state to L1. Default OP config is ~1 hour)

i have a bookmark of all of your greatest hits 🤣

omg what an old dashboard.

Left: Time between BatchInbox transactions (these are the blob-carrying transactions that post batches of L2 transactions to L1) https://specs.optimism.io/glossary.html?highlight=batcher#batcher

Right: Time between State Output Proposals (aka Dispute Games, these are the L2s posting the state to L1. Default OP config is ~1 hour) https://specs.optimism.io/glossary.html?highlight=proposer#proposer