← previous blocknext block →recent activity
Analyzing
Block #96,655,950
8 transactions · 8 stateful · 2026-08-17 02:24:16 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,655,950 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x28be48f5…d50b
0x34b655…2a6f
2 touches
0 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
2 touches
0 conflicts
0x69411fb3…e36d
0x34b655…2a6f
2 touches
0 conflicts
0x9a3463f0…0b73
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eeb
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eec
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 0x91b0f8edc5…b76bd7
Audit this contract →
← previous block·next block →recent activity