← previous blocknext block →recent activity
Analyzing
Block #95,387,929
20 transactions · 18 stateful · 2026-08-12 16:03:34 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,387,929 · 20 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
2w04w05w17w08w29w312w413w515w619w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x442e26a3…e968
0x34b655…2a6f
8 touches
6 conflicts
0xe8146818…5583
0x34b655…2a6f
6 touches
3 conflicts
0xb9d32af9…cb05
0x34b655…2a6f
6 touches
3 conflicts
0x620b761c…270e
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity