← previous blocknext block →recent activity
Analyzing
Block #89,575,718
21 transactions · 19 stateful · 2026-07-23 05:34:00 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,575,718 · 21 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
4w06w17w28w29w310w415w418w019w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69d0a300…67ef
0x34b655…2a6f
8 touches
6 conflicts
0x0422e0ce…38ba
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
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 0x69d0a3001a…3467ef
Audit this contract →
← previous block·next block →recent activity