← previous blocknext block →recent activity
Analyzing
Block #89,858,230
18 transactions · 17 stateful · 2026-07-24 07:32:45 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,858,230 · 18 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
1w02w13w04w18w09w111w212w113w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0x2ad6a439…fd89
0xd32edf…ff58
5 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x181ad9cf…26f4
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x2d030494…3283
0x34b655…2a6f
4 touches
1 conflict
0x3b3e5f00…9a88
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity