← previous blocknext block →recent activity
Analyzing
Block #89,871,119
20 transactions · 18 stateful · 2026-07-24 08:37:35 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,871,119 · 20 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
1w02w03w14w05w06w17w212w013w114w115w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0921dc9d…1c7f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4360b49f…140d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2127ebd5…7b99
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x5d46e6a0…5ed9
0x40c49f…2af0
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 0x0921dc9d14…431c7f
Audit this contract →
← previous block·next block →recent activity