← previous blocknext block →recent activity
Analyzing
Block #89,689,003
15 transactions · 14 stateful · 2026-07-23 17:18:50 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,689,003 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65f36c20…81a4
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x81561f70…fefd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5aff4cb3…c162
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x65f36c20fd…9281a4
Audit this contract →
← previous block·next block →recent activity