← previous blocknext block →recent activity
Analyzing
Block #95,387,277
9 transactions · 7 stateful · 2026-08-12 16:00:16 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,387,277 · 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
1w03w14w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0xe9500ffb…30e8
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x031cd48c…fd30
0x34b655…2a6f
2 touches
0 conflicts
0x036adc97…48eb
0x34b655…2a6f
2 touches
0 conflicts
0x0a3b7ca8…c7f7
0x34b655…2a6f
2 touches
0 conflicts
0x167b8502…d072
0x34b655…2a6f
2 touches
0 conflicts
0x2285ffd3…961c
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 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity