← previous blocknext block →recent activity
Analyzing
Block #91,383,807
25 transactions · 24 stateful · 2026-07-29 15:49:49 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,383,807 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w28w39w410w521w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a056f8…64e4
0x34b655…2a6f
12 touches
15 conflicts
0xd30f9e74…d404
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x94de4d05…ad01
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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
15 conflicts on slot 0x01a056f88f…9b64e4
Audit this contract →
← previous block·next block →recent activity