← previous blocknext block →recent activity
Analyzing
Block #96,083,694
11 transactions · 10 stateful · 2026-08-15 02:25:43 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,083,694 · 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
4w06w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5c56995…6d21
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d22
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x224d6800…4508
0x34b655…2a6f
4 touches
1 conflict
0xa5ab7b8a…c97b
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 0xd5c5699561…d46d21
Audit this contract →
← previous block·next block →recent activity