← previous blocknext block →recent activity
Analyzing
Block #92,009,072
25 transactions · 22 stateful · 2026-07-31 20:16:33 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,009,072 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w08w39w411w016w217w318w423w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1eb410fd…591d
0x34b655…2a6f
8 touches
6 conflicts
0xfb887a94…c508
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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
6 conflicts on slot 0x1eb410fdc2…cd591d
Audit this contract →
← previous block·next block →recent activity