← previous blocknext block →recent activity
Analyzing
Block #95,076,780
19 transactions · 19 stateful · 2026-08-11 13:46:00 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,076,780 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w07w18w29w310w411w212w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 conflicts
0xc6b1d981…1be2
0xa6afd3…d132
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x2dec0e73…3189
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity