← previous blocknext block →recent activity
Analyzing
Block #95,349,691
34 transactions · 28 stateful · 2026-08-12 12:49:50 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.44
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #95,349,691 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w010w111w215w316w418w520w522w723w829w933w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
10 touches
10 conflicts
0x663ff9d7…a77f
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0x32626666…080c
0x34b655…2a6f
6 touches
3 conflicts
0x94de4d05…ad01
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity