← previous blocknext block →recent activity
Analyzing
Block #91,962,026
22 transactions · 19 stateful · 2026-07-31 16:19:56 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,962,026 · 22 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
1w02w15w28w212w013w114w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889c005d…32d5
0x7b9256…1fb2
6 touches
3 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x14c004e4…835b
0x7b9256…1fb2
6 touches
3 conflicts
0x14c004e4…835c
0x7b9256…1fb2
6 touches
3 conflicts
0x889c005d…32d1
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0x889c005d2a…c532d5
Audit this contract →
← previous block·next block →recent activity