← previous blocknext block →recent activity
Analyzing
Block #89,567,075
11 transactions · 10 stateful · 2026-07-23 04:36:14 UTC
Parallelism
55/100
Blocked
60%
Avg conflicts / tx
1.09
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,567,075 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w47w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53d143c8…312d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x5f394770…ac95
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 0x53d143c84d…38312d
Audit this contract →
← previous block·next block →recent activity