← previous blocknext block →recent activity
Analyzing
Block #95,397,649
18 transactions · 17 stateful · 2026-08-12 16:52:45 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
2.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #95,397,649 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w58w612w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x1d2affc9…7d67
0x34b655…2a6f
10 touches
10 conflicts
0x4efae872…6aa8
0x34b655…2a6f
10 touches
10 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
6 touches
3 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x93ffcd76…894e
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity