← previous blocknext block →recent activity
Analyzing
Block #91,131,055
20 transactions · 17 stateful · 2026-07-28 18:37:15 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,131,055 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w19w311w012w413w117w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xa783e0e5…83f7
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0x589623ea…8ce2
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity