← previous blocknext block →recent activity
Analyzing
Block #96,509,517
11 transactions · 9 stateful · 2026-08-16 14:07:46 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,509,517 · 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
1w06w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaafc0c3d…64b6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xe624cb16…9dc0
0x34b655…2a6f
4 touches
1 conflict
0x27f75f20…525c
0x34b655…2a6f
2 touches
0 conflicts
0x2d94ecd9…43db
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 0xaafc0c3d1e…2464b6
Audit this contract →
← previous block·next block →recent activity