← previous blocknext block →recent activity
Analyzing
Block #105,627,335
20 transactions · 19 stateful · 2026-09-17 14:18:57 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,627,335 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w19w110w211w314w115w216w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe6f4d761…dbab
0x34b655…2a6f
6 touches
3 conflicts
0x461c1f9d…a158
0x34b655…2a6f
4 touches
1 conflict
0x4f18bcdc…fd17
0x34b655…2a6f
4 touches
1 conflict
0x4f526c44…ba6f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x58138cee…d3d3
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity