← previous blocknext block →recent activity
Analyzing
Block #91,296,849
17 transactions · 17 stateful · 2026-07-29 08:32:11 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,296,849 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w110w211w212w113w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4b4befb6…0aed
0x34b655…2a6f
6 touches
3 conflicts
0xf5899760…c130
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
3 conflicts on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity