← previous blocknext block →recent activity
Analyzing
Block #89,667,014
11 transactions · 9 stateful · 2026-07-23 15:27:09 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,667,014 · 11 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
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80656e3b…9240
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x89c4fedf…b215
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
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
3 conflicts on slot 0x80656e3b9f…e39240
Audit this contract →
← previous block·next block →recent activity