← previous blocknext block →recent activity
Analyzing
Block #89,859,937
23 transactions · 21 stateful · 2026-07-24 07:41:20 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,859,937 · 23 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
4w06w17w28w310w311w412w516w619w620w722w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65398157…785c
0x34b655…2a6f
10 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xe3eedc4b…dd93
0x34b655…2a6f
8 touches
6 conflicts
0x4360b49f…140d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x6539815791…b0785c
Audit this contract →
← previous block·next block →recent activity