← previous blocknext block →recent activity
Analyzing
Block #89,544,436
22 transactions · 19 stateful · 2026-07-23 02:05:00 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,544,436 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w111w212w313w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
8 touches
6 conflicts
0x5b7ab4c4…1a0d
0x34b655…2a6f
6 touches
3 conflicts
0x23d654fc…ecd8
0x34b655…2a6f
6 touches
3 conflicts
0x4d6d40ed…e2ce
0x34b655…2a6f
6 touches
3 conflicts
0x9c2fc330…0091
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity