← previous blocknext block →recent activity
Analyzing
Block #106,377,353
34 transactions · 34 stateful · 2026-09-20 05:16:12 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
2.32
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,377,353 · 34 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w18w19w212w215w317w221w322w423w524w625w726w827w928w1029w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
14 touches
21 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
12 touches
15 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
12 touches
15 conflicts
0x4068d9ca…5fc5
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity