← previous blocknext block →recent activity
Analyzing
Block #89,854,958
32 transactions · 29 stateful · 2026-07-24 07:16:18 UTC
Parallelism
75/100
Blocked
69%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,854,958 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w27w38w49w010w111w212w320w221w423w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x897df0ee…b0c5
0x40c49f…2af0
6 touches
3 conflicts
0x0413d1ed…ad55
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity