← previous blocknext block →recent activity
Analyzing
Block #95,152,125
41 transactions · 36 stateful · 2026-08-11 20:05:01 UTC
Parallelism
54/100
Blocked
75%
Avg conflicts / tx
2.9
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #95,152,125 · 41 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w08w19w210w311w412w513w614w117w625w926w1027w1136w1637w339w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x424934c8…f2f1
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block·next block →recent activity