← previous blocknext block →recent activity
Analyzing
Block #89,515,754
19 transactions · 19 stateful · 2026-07-22 22:53:27 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,515,754 · 19 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
1w02w13w24w35w06w07w110w111w012w113w215w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bac71c3…3296
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0f1cee53…5f80
0x34b655…2a6f
4 touches
1 conflict
0x1e120cc8…7049
0x34b655…2a6f
4 touches
1 conflict
0x2debe664…1818
0x34b655…2a6f
4 touches
1 conflict
0x304a552a…8fc7
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 0x2bac71c3f0…0a3296
Audit this contract →
← previous block·next block →recent activity