← previous blocknext block →recent activity
Analyzing
Block #87,699,643
26 transactions · 25 stateful · 2026-07-14 12:26:30 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,699,643 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w110w011w112w213w315w116w317w418w519w620w725w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d6d235c…3d64
0x34b655…2a6f
14 touches
21 conflicts
0xc36fa358…24cb
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x9e70dadd…810e
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
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 0x9d6d235c04…a13d64
Audit this contract →
← previous block·next block →recent activity