← previous blocknext block →recent activity
Analyzing
Block #96,256,988
9 transactions · 7 stateful · 2026-08-15 16:57:22 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,256,988 · 9 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x0eaa3f4e…2992
0x34b655…2a6f
4 touches
1 conflict
0x575f6146…c232
0x34b655…2a6f
4 touches
1 conflict
0xa2b263c3…4c49
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0dd7d6d8…3700
0x34b655…2a6f
2 touches
0 conflicts
0x3284a5dd…2c32
0x34b655…2a6f
2 touches
0 conflicts
0x478aa196…f156
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity