← previous blocknext block →recent activity
Analyzing
Block #90,955,764
17 transactions · 16 stateful · 2026-07-28 03:54:28 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,955,764 · 17 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
1w02w13w04w15w26w37w09w410w413w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x142de65e…87ed
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x29f26b03…63b1
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
0x34b655…2a6f
4 touches
1 conflict
0x52c65a03…b027
0x34b655…2a6f
4 touches
1 conflict
0x5abb42a7…8507
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity