← previous blocknext block →recent activity
Analyzing
Block #87,063,618
66 transactions · 49 stateful · 2026-07-11 13:32:40 UTC
Parallelism
65/100
Blocked
76%
Avg conflicts / tx
3.73
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,063,618 · 66 txs across 23 waves · depth 23
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
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w17w210w313w416w519w626w127w152w653w754w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…00c9
0x34b655…2a6f
20 touches
45 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
18 touches
36 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
16 touches
28 conflicts
0x2328941c…84d3
0x34b655…2a6f
16 touches
28 conflicts
0x2484cc15…5afc
0x34b655…2a6f
16 touches
28 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity