← previous blocknext block →recent activity
Analyzing
Block #95,746,599
10 transactions · 8 stateful · 2026-08-13 22:09:43 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,746,599 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24fdc9d0…a23a
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x3ad8bbeb…b084
0x34b655…2a6f
2 touches
0 conflicts
0x66a40782…f16e
0x34b655…2a6f
2 touches
0 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
2 touches
0 conflicts
0x6e1a553c…2153
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x24fdc9d0a9…26a23a
Audit this contract →
← previous block·next block →recent activity