← previous blocknext block →recent activity
Analyzing
Block #95,975,249
26 transactions · 21 stateful · 2026-08-14 17:20:06 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,975,249 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w29w110w211w312w418w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12c9f069…0bda
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x29c1a140…099f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0728ec77…146c
0x34b655…2a6f
4 touches
1 conflict
0x3ebb403d…3a8f
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
6 conflicts on slot 0x12c9f06903…5c0bda
Audit this contract →
← previous block·next block →recent activity