← previous blocknext block →recent activity
Analyzing
Block #87,517,648
24 transactions · 23 stateful · 2026-07-13 16:09:03 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,517,648 · 24 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
1w03w04w05w16w29w010w111w314w216w120w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ce640b…884a
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x70297431…dc19
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x46b62326…9b3c
0xa6afd3…d132
6 touches
3 conflicts
0x89750670…2dea
0xa6afd3…d132
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 0x69ce640b96…ed884a
Audit this contract →
← previous block·next block →recent activity