← previous blocknext block →recent activity
Analyzing
Block #96,666,914
16 transactions · 16 stateful · 2026-08-17 03:19:25 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,666,914 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w614w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
14 touches
21 conflicts
0x8b87ece6…3353
0x34b655…2a6f
6 touches
3 conflicts
0xa27f1875…0c5d
0x34b655…2a6f
6 touches
3 conflicts
0xa9f8096f…f132
0x34b655…2a6f
6 touches
3 conflicts
0x6aef82db…28d6
0x34b655…2a6f
6 touches
3 conflicts
0xd9dcb336…ee08
0x34b655…2a6f
6 touches
3 conflicts
0xdbd174e4…b6f8
0x34b655…2a6f
6 touches
3 conflicts
0x75586248…f0b4
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity