← previous blocknext block →recent activity
Analyzing
Block #96,828,797
13 transactions · 11 stateful · 2026-08-17 16:53:38 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,828,797 · 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
2w03w04w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f79a461…5c8f
0x34b655…2a6f
6 touches
3 conflicts
0xd459bf7b…92c3
0x34b655…2a6f
6 touches
3 conflicts
0x84032a94…ed1f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x352cdf9c…2863
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xbb96f8af…205f
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 0x1f79a461c3…455c8f
Audit this contract →
← previous block·next block →recent activity