← previous blocknext block →recent activity
Analyzing
Block #89,528,310
26 transactions · 24 stateful · 2026-07-23 00:17:18 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,528,310 · 26 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
1w02w03w04w17w08w110w011w212w214w316w419w521w623w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf2177ea9…8355
0x34b655…2a6f
8 touches
6 conflicts
0xf609f09b…f03a
0x34b655…2a6f
6 touches
3 conflicts
0xe3cfa4f0…bfdf
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a84c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity