← previous blocknext block →recent activity
Analyzing
Block #91,387,910
25 transactions · 19 stateful · 2026-07-29 16:10:27 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,387,910 · 25 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
7w08w111w212w313w414w517w518w322w023w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x20fbcaee…bb79
0x34b655…2a6f
4 touches
1 conflict
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x3c0c2f32…c3df
0x34b655…2a6f
4 touches
1 conflict
0x4905be8a…073f
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x58622c15…4dee
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity