← previous blocknext block →recent activity
Analyzing
Block #96,023,267
12 transactions · 12 stateful · 2026-08-14 21:21:46 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,023,267 · 12 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
1w02w05w16w28w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe30c1f62…49ae
0x34b655…2a6f
6 touches
3 conflicts
0xffe7fbbe…9fa5
0x34b655…2a6f
6 touches
3 conflicts
0x27b96981…ef48
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc2cce19d…4ad4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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 0xe30c1f6268…f649ae
Audit this contract →
← previous block·next block →recent activity