← previous blocknext block →recent activity
Analyzing
Block #105,608,198
35 transactions · 32 stateful · 2026-09-17 12:42:36 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1.6
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,608,198 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w17w221w322w423w524w625w727w828w929w1033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ecbbe7…f713
0x34b655…2a6f
18 touches
36 conflicts
0x0cbce40b…c4b6
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x76da8d77…bc80
0x34b655…2a6f
10 touches
10 conflicts
0xd7da0750…565e
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
36 conflicts on slot 0xa7ecbbe767…04f713
Audit this contract →
← previous block·next block →recent activity