← previous blocknext block →recent activity
Analyzing
Block #92,600,320
12 transactions · 11 stateful · 2026-08-02 21:50:07 UTC
Parallelism
33/100
Blocked
64%
Avg conflicts / tx
2.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,600,320 · 12 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
1w02w13w25w36w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xa779293b…5e59
0x34b655…2a6f
10 touches
10 conflicts
0x32b7e349…5f63
0x34b655…2a6f
10 touches
10 conflicts
0xbe9baf16…df37
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0xc5c8022c…8d1f
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity