← previous blocknext block →recent activity
Analyzing
Block #91,136,154
20 transactions · 19 stateful · 2026-07-28 19:02:54 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,136,154 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w37w09w010w116w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b8d9164…5b0c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x53cb95c5…2986
0xd32edf…ff58
7 touches
6 conflicts
0x78cb41e1…f2c1
0xfa32f9…f3f0
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
6 touches
3 conflicts
0x95dd1dda…bc0e
0x34b655…2a6f
6 touches
3 conflicts
0xa51de3df…c65a
0x34b655…2a6f
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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
6 conflicts on slot 0x2b8d91642b…475b0c
Audit this contract →
← previous block·next block →recent activity