← previous blocknext block →recent activity
Analyzing
Block #95,150,899
10 transactions · 10 stateful · 2026-08-11 19:58:51 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,150,899 · 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
2w04w15w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc139c876…fe04
0x34b655…2a6f
4 touches
1 conflict
0xb416438e…796a
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0xf18e87f5…6880
0x34b655…2a6f
4 touches
1 conflict
0x53d526f9…1ab8
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
2 touches
0 conflicts
0x8d0bf98a…b467
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
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 0xc139c876e0…9bfe04
Audit this contract →
← previous block·next block →recent activity