← previous blocknext block →recent activity
Analyzing
Block #95,128,386
9 transactions · 6 stateful · 2026-08-11 18:05:36 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,128,386 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa065de59…3f32
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x7c37629d…9e3f
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x0a50ba88…7027
0x34b655…2a6f
2 touches
0 conflicts
0x0dfc6550…fe5d
0x34b655…2a6f
2 touches
0 conflicts
0x24742942…0c3d
0x34b655…2a6f
2 touches
0 conflicts
0x2655625d…b058
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
1 conflict on slot 0xa065de598b…c63f32
Audit this contract →
← previous block·next block →recent activity