← previous blocknext block →recent activity
Analyzing
Block #96,652,639
12 transactions · 12 stateful · 2026-08-17 02:07:37 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,652,639 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w27w08w110w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd6ccd20…c33e
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x553d09ad…e640
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
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 0xcd6ccd2062…74c33e
Audit this contract →
← previous block·next block →recent activity