← previous blocknext block →recent activity
Analyzing
Block #92,063,778
17 transactions · 15 stateful · 2026-08-01 00:51:41 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,063,778 · 17 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
2w03w15w06w17w08w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67708716…f9b6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x278c4ae5…1639
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x6c0bfcd8…55a7
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
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
6 conflicts on slot 0x67708716f8…89f9b6
Audit this contract →
← previous block·next block →recent activity