← previous blocknext block →recent activity
Analyzing
Block #87,594,685
20 transactions · 19 stateful · 2026-07-14 00:44:57 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,594,685 · 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
1w02w13w24w35w06w07w18w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x7a12283f…b18a
0x2b46c0…1669
6 touches
3 conflicts
0x80caf0f7…f2de
0x2b46c0…1669
6 touches
3 conflicts
0x915c095e…c1e5
0x2b46c0…1669
6 touches
3 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
6 touches
3 conflicts
0x053c1f05…4b0b
0x34b655…2a6f
6 touches
3 conflicts
0x42341814…60f1
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity