← previous blocknext block →recent activity
Analyzing
Block #106,541,216
40 transactions · 36 stateful · 2026-09-20 19:00:57 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,541,216 · 40 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
3w04w15w06w17w18w213w220w322w128w229w430w531w632w633w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc973852…d99a
0x34b655…2a6f
12 touches
15 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0xf91d37c7…39f1
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x4acd9e51…2863
0x34b655…2a6f
8 touches
6 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
8 touches
6 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xcc973852c0…82d99a
Audit this contract →
← previous block·next block →recent activity