← previous blocknext block →recent activity
Analyzing
Block #92,571,297
17 transactions · 17 stateful · 2026-08-02 19:24:08 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,571,297 · 17 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
3w04w15w26w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38232bf9…db72
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x620b761c…270e
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
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 0x38232bf93d…8fdb72
Audit this contract →
← previous block·next block →recent activity