← previous blocknext block →recent activity
Analyzing
Block #91,797,139
25 transactions · 22 stateful · 2026-07-31 02:30:23 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,797,139 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w313w115w216w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x772ab420…c2f6
0x34b655…2a6f
10 touches
10 conflicts
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0xfecb18c0…01ed
0x34b655…2a6f
8 touches
6 conflicts
0x7bb8bdfc…f677
0x34b655…2a6f
6 touches
3 conflicts
0xbd71e14b…864c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity