← previous blocknext block →recent activity
Analyzing
Block #96,638,925
26 transactions · 23 stateful · 2026-08-17 00:58:38 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,638,925 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w19w210w313w414w015w316w417w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x0cef9392…c35e
0xd32edf…ff58
9 touches
10 conflicts
0x5e9fece6…173f
0x34b655…2a6f
8 touches
6 conflicts
0x82f1549d…82c3
0x34b655…2a6f
8 touches
6 conflicts
0x31616f97…1acc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x12bf5c77…5588
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity