← previous blocknext block →recent activity
Analyzing
Block #106,435,226
22 transactions · 20 stateful · 2026-09-20 10:07:28 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,435,226 · 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
1w02w15w06w17w09w111w212w313w414w515w616w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a6b4037…febd
0x34b655…2a6f
10 touches
10 conflicts
0x000bde1a…e123
0x34b655…2a6f
8 touches
6 conflicts
0x2c50a004…b887
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7cd9fd28…a158
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
10 conflicts on slot 0x2a6b40371b…66febd
Audit this contract →
← previous block·next block →recent activity