← previous blocknext block →recent activity
Analyzing
Block #87,723,876
35 transactions · 30 stateful · 2026-07-14 15:09:00 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,723,876 · 35 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
1w02w13w24w05w19w010w111w214w015w216w317w418w519w620w221w330w332w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x9eb9f318…dfd2
0xd32edf…ff58
7 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x5e4b65e1…ebe1
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity