← previous blocknext block →recent activity
Analyzing
Block #87,595,185
63 transactions · 54 stateful · 2026-07-14 00:48:17 UTC
Parallelism
68/100
Blocked
76%
Avg conflicts / tx
3.43
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,595,185 · 63 txs across 20 waves · depth 20
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
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w29w010w111w212w313w014w115w228w529w630w731w841w543w345w251w452w553w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x69ce640b…884a
0x34b655…2a6f
16 touches
28 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0001
0xc1ff9f…b0fc
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
10 touches
10 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
10 touches
10 conflicts
0xd11dcf4e…518f
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity