← previous blocknext block →recent activity
Analyzing
Block #95,278,533
9 transactions · 9 stateful · 2026-08-12 06:49:42 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,278,533 · 9 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
1w03w14w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd6
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x0b7c26e8…c3ad
0x34b655…2a6f
2 touches
0 conflicts
0x0bbc9941…4358
0x34b655…2a6f
2 touches
0 conflicts
0x1deed43d…5768
0x34b655…2a6f
2 touches
0 conflicts
0x3f40bee4…8226
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
3 conflicts on slot 0x91b0f8edc5…b76bd6
Audit this contract →
← previous block·next block →recent activity