← previous blocknext block →recent activity
Analyzing
Block #96,600,303
14 transactions · 12 stateful · 2026-08-16 21:44:23 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,600,303 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w210w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34d95d94…3a16
0x34b655…2a6f
8 touches
6 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
8 touches
6 conflicts
0x0d488000…3831
0x34b655…2a6f
8 touches
6 conflicts
0xf796eaef…fac5
0x34b655…2a6f
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
6 touches
3 conflicts
0x733de0a2…0690
0x34b655…2a6f
6 touches
3 conflicts
0x8a1db511…3ac9
0x34b655…2a6f
6 touches
3 conflicts
0x99479bc5…3a88
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
6 conflicts on slot 0x34d95d945c…603a16
Audit this contract →
← previous block·next block →recent activity