← previous blocknext block →recent activity
Analyzing
Block #95,156,460
24 transactions · 23 stateful · 2026-08-11 20:26:49 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,156,460 · 24 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
3w04w15w26w37w08w49w110w214w315w519w620w423w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b572464…fc51
0x34b655…2a6f
10 touches
10 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
10 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x831dbc32…b84a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
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
10 conflicts on slot 0x4b57246402…5bfc51
Audit this contract →
← previous block·next block →recent activity