← previous blocknext block →recent activity
Analyzing
Block #89,586,144
15 transactions · 13 stateful · 2026-07-23 06:43:34 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,586,144 · 15 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
3w04w18w29w310w411w512w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c59a6a5…6915
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x69d0a300…67ef
0x34b655…2a6f
6 touches
3 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbb924223…aba2
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x7c59a6a517…156915
Audit this contract →
← previous block·next block →recent activity