← previous blocknext block →recent activity
Analyzing
Block #95,413,117
10 transactions · 10 stateful · 2026-08-12 18:11:05 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,413,117 · 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba84f67…de6e
0x34b655…2a6f
6 touches
3 conflicts
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0x478e71ff…6cc6
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x05527801…9c11
0x34b655…2a6f
4 touches
1 conflict
0xeba56708…8cd7
0x2b46c0…1669
2 touches
0 conflicts
0x210e4f42…9aa2
0x34b655…2a6f
2 touches
0 conflicts
0x2d307ea7…8841
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 0x9ba84f67c9…7ade6e
Audit this contract →
← previous block·next block →recent activity