← previous blocknext block →recent activity
Analyzing
Block #105,583,175
16 transactions · 15 stateful · 2026-09-17 10:36:38 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,583,175 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6393111f…e66f
0x34b655…2a6f
8 touches
6 conflicts
0xf72228f6…970c
0x34b655…2a6f
8 touches
6 conflicts
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0x818e1296…f4d7
0x34b655…2a6f
4 touches
1 conflict
0xfc2493d3…6898
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x213b816c…a5e0
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0x6393111ff2…35e66f
Audit this contract →
← previous block·next block →recent activity