← previous blocknext block →recent activity
Analyzing
Block #89,526,032
27 transactions · 26 stateful · 2026-07-23 00:02:09 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
1.15
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #89,526,032 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w010w111w212w313w414w515w016w618w620w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x94ddea60…a24d
0x34b655…2a6f
6 touches
3 conflicts
0x9a65844d…54c8
0x34b655…2a6f
6 touches
3 conflicts
0x50260e8c…4789
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xb5924647…4cf1
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity