← previous blocknext block →recent activity
Analyzing
Block #89,858,418
11 transactions · 10 stateful · 2026-07-24 07:33:42 UTC
Parallelism
36/100
Blocked
60%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,858,418 · 11 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
3w04w16w27w38w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x03aa8b26…118a
0x34b655…2a6f
6 touches
3 conflicts
0x024a7f41…8af8
0x34b655…2a6f
6 touches
3 conflicts
0x353a3a00…5e0a
0x34b655…2a6f
6 touches
3 conflicts
0x4886b3df…67a3
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x747f609d…1555
0x34b655…2a6f
6 touches
3 conflicts
0xa51de3df…c65a
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity