← previous blocknext block →recent activity
Analyzing
Block #95,033,149
13 transactions · 12 stateful · 2026-08-11 10:05:51 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,033,149 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x82f46d1e…1831
0x34b655…2a6f
3 touches
1 conflict
0x01f79234…056b
0x34b655…2a6f
3 touches
1 conflict
0x025fef2f…9738
0x34b655…2a6f
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x478e71ff…6cc6
0x34b655…2a6f
2 touches
0 conflicts
0x4b97b5fa…b3ae
0x34b655…2a6f
2 touches
0 conflicts
0x59dccbd8…2bf6
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity