← previous blocknext block →recent activity
Analyzing
Block #106,570,291
22 transactions · 18 stateful · 2026-09-20 21:27:16 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,570,291 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w212w014w115w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4089d428…b018
0x34b655…2a6f
14 touches
21 conflicts
0x6dcc4bf3…eb84
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xfe2577ac…677b
0x34b655…2a6f
8 touches
6 conflicts
0xc7704bc1…a4f7
0x34b655…2a6f
8 touches
6 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 conflicts
0x29fd1ca5…a88a
0x34b655…2a6f
6 touches
3 conflicts
0x474b8a4d…2f29
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
21 conflicts on slot 0x4089d42830…afb018
Audit this contract →
← previous block·next block →recent activity