← previous blocknext block →recent activity
Analyzing
Block #87,520,317
35 transactions · 28 stateful · 2026-07-13 16:27:04 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
1.69
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,520,317 · 35 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w17w29w010w011w115w216w317w418w519w620w721w822w926w1027w328w430w133w1034w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
14 touches
21 conflicts
0xc3688185…9b36
0x34b655…2a6f
12 touches
15 conflicts
0x9d6d235c…3d64
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xb4c35fcd…43ae
0xa6afd3…d132
8 touches
6 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
21 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity