← previous blocknext block →recent activity
Analyzing
Block #95,005,915
21 transactions · 16 stateful · 2026-08-11 07:48:43 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,005,915 · 21 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
1w02w16w17w111w012w113w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6c51e22…fbfb
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xfc24540b…6463
0x34b655…2a6f
6 touches
3 conflicts
0x844bbdaa…7b66
0x065c9d…c394
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb193c4fa…4abd
0x34b655…2a6f
4 touches
1 conflict
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 0xc6c51e2202…1afbfb
Audit this contract →
← previous block·next block →recent activity