← previous blocknext block →recent activity
Analyzing
Block #91,190,871
34 transactions · 26 stateful · 2026-07-28 23:38:10 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,190,871 · 34 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
1w02w13w04w15w27w18w09w113w014w115w217w321w322w323w329w431w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
6 touches
3 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0xb56f0740…7542
0x34b655…2a6f
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0xeba56708…8cd7
0x2b46c0…1669
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity