← previous blocknext block →recent activity
Analyzing
Block #89,528,124
27 transactions · 24 stateful · 2026-07-23 00:16:04 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,528,124 · 27 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
1w03w04w15w27w08w19w210w311w312w413w315w516w321w625w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x405da62e…192a
0xa6afd3…d132
6 touches
3 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0xafc39832…fb69
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity