← previous blocknext block →recent activity
Analyzing
Block #95,710,664
22 transactions · 20 stateful · 2026-08-13 19:08:48 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,710,664 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w09w210w311w412w513w619w020w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x4efae872…6aa8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0xd597209e…9800
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x8d3befc2…74a8
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity