← previous blocknext block →recent activity
Analyzing
Block #89,711,130
20 transactions · 20 stateful · 2026-07-23 19:10:20 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,711,130 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w311w012w113w214w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0x9932c6d5…0e65
0x0a2fbf…29b1
8 touches
6 conflicts
0x9932c6d5…0e66
0x0a2fbf…29b1
8 touches
6 conflicts
0x9932c6d5…0e69
0x0a2fbf…29b1
8 touches
6 conflicts
0xbfe60507…e208
0x0a2fbf…29b1
8 touches
6 conflicts
0xbfe60507…e209
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 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 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity