← previous blocknext block →recent activity
Analyzing
Block #96,083,697
13 transactions · 11 stateful · 2026-08-15 02:25:44 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,083,697 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0x4d971bc9…fadc
0x34b655…2a6f
6 touches
3 conflicts
0x940d347c…0095
0x34b655…2a6f
5 touches
3 conflicts
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x37d79cfc…b8e5
0x34b655…2a6f
4 touches
1 conflict
0x458b9085…9ee2
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
3 conflicts on slot 0xb256030504…6df27d
Audit this contract →
← previous block·next block →recent activity