← previous blocknext block →recent activity
Analyzing
Block #96,307,683
19 transactions · 18 stateful · 2026-08-15 21:12:20 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,307,683 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w28w210w011w112w213w314w415w516w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf89542f…7537
0x968279…9342
12 touches
15 conflicts
0x521a5982…a82a
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0x25d1e3f7…0437
0x968279…9342
12 touches
15 conflicts
0x25d1e3f7…0438
0x968279…9342
12 touches
15 conflicts
0x25d1e3f7…043a
0x968279…9342
12 touches
15 conflicts
0xaf89542f…7530
0x968279…9342
12 touches
15 conflicts
0xaf89542f…7531
0x968279…9342
12 touches
15 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: 0x96827978…f09342
15 conflicts on slot 0xaf89542f64…617537
Audit this contract →
← previous block·next block →recent activity