← previous blocknext block →recent activity
Analyzing
Block #96,036,988
13 transactions · 13 stateful · 2026-08-14 22:30:49 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,036,988 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w19w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcedd9c7b…916e
0x34b655…2a6f
4 touches
1 conflict
0x06d2a0e6…2154
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x1b4287c5…81c8
0x34b655…2a6f
4 touches
1 conflict
0x65f773b6…46cc
0x34b655…2a6f
4 touches
1 conflict
0x7b481037…3457
0x34b655…2a6f
4 touches
1 conflict
0x7ea60711…6098
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
1 conflict on slot 0xcedd9c7b7e…dc916e
Audit this contract →
← previous block·next block →recent activity