← previous blocknext block →recent activity
Analyzing
Block #95,852,660
16 transactions · 14 stateful · 2026-08-14 07:03:10 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,852,660 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w110w211w312w013w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35a9f06c…7689
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x086e7ab4…ed30
0x065c9d…c394
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa74d6ebc…fddf
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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
6 conflicts on slot 0x35a9f06ccf…e37689
Audit this contract →
← previous block·next block →recent activity