← previous blocknext block →recent activity
Analyzing
Block #95,077,582
38 transactions · 38 stateful · 2026-08-11 13:50:02 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,077,582 · 38 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w27w38w210w329w431w132w233w334w437w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb03f96de…b58b
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
6 touches
3 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x45ea7a97…bbb3
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
3 conflicts on slot 0xb03f96de54…73b58b
Audit this contract →
← previous block·next block →recent activity