← previous blocknext block →recent activity
Analyzing
Block #89,538,683
14 transactions · 14 stateful · 2026-07-23 01:26:32 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,538,683 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x04994ed2…9032
0x34b655…2a6f
6 touches
3 conflicts
0xeb403811…08ce
0x34b655…2a6f
6 touches
3 conflicts
0x9655d334…462e
0x34b655…2a6f
4 touches
3 conflicts
0x3f4f9f22…8ad6
0x34b655…2a6f
4 touches
1 conflict
0x4599e0b9…e177
0x34b655…2a6f
4 touches
1 conflict
0x4cbef8cc…2aa4
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
3 conflicts on slot 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity