← previous blocknext block →recent activity
Analyzing
Block #96,786,782
15 transactions · 14 stateful · 2026-08-17 13:22:18 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,786,782 · 15 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
1w03w04w06w19w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0xb3c13127…3ae1
0x34b655…2a6f
4 touches
1 conflict
0xcf61bee7…8662
0x34b655…2a6f
4 touches
1 conflict
0xe23de992…a021
0x34b655…2a6f
4 touches
1 conflict
0xe9991812…e391
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity