← previous blocknext block →recent activity
Analyzing
Block #106,199,426
26 transactions · 22 stateful · 2026-09-19 14:20:41 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,199,426 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w07w19w210w316w017w119w020w121w222w324w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dc6c70d…37a6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5717771c…45ed
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xcfe180d7…b5a4
0x34b655…2a6f
6 touches
3 conflicts
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x8dc6c70d97…ce37a6
Audit this contract →
← previous block·next block →recent activity