← previous blocknext block →recent activity
Analyzing
Block #89,587,896
26 transactions · 20 stateful · 2026-07-23 06:55:16 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,587,896 · 26 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
3w04w06w17w29w010w112w013w114w218w120w121w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8d5fb8…f457
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x28c714d9…9438
0xa6afd3…d132
4 touches
1 conflict
0xb566cc65…214d
0xa6afd3…d132
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 0x4e8d5fb8fc…3ef457
Audit this contract →
← previous block·next block →recent activity