← previous blocknext block →recent activity
Analyzing
Block #96,694,813
20 transactions · 17 stateful · 2026-08-17 05:39:43 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,694,813 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w27w38w313w014w415w117w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03aa8b26…118a
0x34b655…2a6f
8 touches
6 conflicts
0x2840c278…bbc7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf58eca50…59f6
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x03aa8b260f…60118a
Audit this contract →
← previous block·next block →recent activity