← previous blocknext block →recent activity
Analyzing
Block #96,706,595
13 transactions · 11 stateful · 2026-08-17 06:38:59 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,706,595 · 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
9w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49141cce…8f8f
0x34b655…2a6f
4 touches
1 conflict
0x1eced4db…6e94
0x34b655…2a6f
2 touches
0 conflicts
0x2d8c4f06…f538
0x34b655…2a6f
2 touches
0 conflicts
0x390dd46c…deef
0x34b655…2a6f
2 touches
0 conflicts
0x3e950538…2259
0x34b655…2a6f
2 touches
0 conflicts
0x495f2eb1…7b0a
0x34b655…2a6f
2 touches
0 conflicts
0x55803256…09e9
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity