← previous blocknext block →recent activity
Analyzing
Block #95,160,618
12 transactions · 12 stateful · 2026-08-11 20:47:44 UTC
Parallelism
42/100
Blocked
58%
Avg conflicts / tx
1.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,160,618 · 12 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
1w02w13w04w15w26w37w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9baf16…df37
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
8 touches
6 conflicts
0xfdf81312…1dc8
0x34b655…2a6f
8 touches
6 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x77ab3b32…6ce4
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 0xbe9baf16a9…e6df37
Audit this contract →
← previous block·next block →recent activity