← previous blocknext block →recent activity
Analyzing
Block #106,555,973
31 transactions · 26 stateful · 2026-09-20 20:15:12 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
1.74
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,555,973 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w09w110w212w114w316w517w619w121w122w723w725w926w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56b5f6e…e64a
0x34b655…2a6f
18 touches
36 conflicts
0x810a3aa2…0227
0x34b655…2a6f
14 touches
21 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
12 touches
15 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xb654bd89…a83b
0x34b655…2a6f
6 touches
3 conflicts
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
36 conflicts on slot 0xa56b5f6ef6…ede64a
Audit this contract →
← previous block·next block →recent activity