← previous blocknext block →recent activity
Analyzing
Block #95,975,619
10 transactions · 9 stateful · 2026-08-14 17:21:58 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,975,619 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cc1ec8e…be2f
0x34b655…2a6f
6 touches
3 conflicts
0x74137b07…5880
0x34b655…2a6f
4 touches
1 conflict
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xb7fb89e5…b3c8
0x34b655…2a6f
3 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
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
3 conflicts on slot 0x1cc1ec8e36…6abe2f
Audit this contract →
← previous block·next block →recent activity