← previous blocknext block →recent activity
Analyzing
Block #95,382,263
13 transactions · 12 stateful · 2026-08-12 15:34:54 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,382,263 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64461c10…e86d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x989252a1…d812
0xa6afd3…d132
4 touches
1 conflict
0x620b761c…270e
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xf16b5107…7cdb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
3 conflicts on slot 0x64461c10d4…d1e86d
Audit this contract →
← previous block·next block →recent activity