← previous blocknext block →recent activity
Analyzing
Block #92,202,370
11 transactions · 11 stateful · 2026-08-01 12:28:42 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,202,370 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x44331cd1…15b0
0x34b655…2a6f
4 touches
1 conflict
0x03b2c1a8…c29f
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x152a7024…b61f
0x34b655…2a6f
2 touches
0 conflicts
0x2d76276f…7c66
0x34b655…2a6f
2 touches
0 conflicts
0x2f4b1dc8…e9fa
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity