← previous blocknext block →recent activity
Analyzing
Block #96,701,772
11 transactions · 9 stateful · 2026-08-17 06:14:43 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,701,772 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a296f2d…2630
0x34b655…2a6f
4 touches
1 conflict
0x12e8fcf0…63bb
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x3bb86768…2a71
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
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
1 conflict on slot 0x2a296f2d92…9d2630
Audit this contract →
← previous block·next block →recent activity