← previous blocknext block →recent activity
Analyzing
Block #89,688,127
17 transactions · 17 stateful · 2026-07-23 17:14:24 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,688,127 · 17 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
1w03w14w25w36w48w59w611w616w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x98212952…9ba6
0x34b655…2a6f
8 touches
6 conflicts
0x81561f70…fefd
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x77aa2f01…8939
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity