← previous blocknext block →recent activity
Analyzing
Block #106,956,466
23 transactions · 20 stateful · 2026-09-22 05:51:57 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,956,466 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w19w210w314w115w216w417w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb77b424a…9a25
0x34b655…2a6f
10 touches
10 conflicts
0x4ebd9eec…d5c3
0x34b655…2a6f
10 touches
10 conflicts
0x8590b692…b267
0x34b655…2a6f
8 touches
6 conflicts
0x3b332c85…8be6
0x34b655…2a6f
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity