← previous blocknext block →recent activity
Analyzing
Block #96,438,659
12 transactions · 12 stateful · 2026-08-16 08:11:04 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,438,659 · 12 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
2w03w05w19w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x827557c1…a6be
0x34b655…2a6f
8 touches
6 conflicts
0x86c98782…f3b7
0x34b655…2a6f
6 touches
3 conflicts
0xc7277122…8339
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7f63a266…68c0
0x34b655…2a6f
5 touches
3 conflicts
0x5625ec2a…00f2
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
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
6 conflicts on slot 0x827557c160…8da6be
Audit this contract →
← previous block·next block →recent activity