← previous blocknext block →recent activity
Analyzing
Block #87,699,922
68 transactions · 51 stateful · 2026-07-14 12:28:22 UTC
Parallelism
71/100
Blocked
78%
Avg conflicts / tx
3.19
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,699,922 · 68 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
1w02w16w07w18w19w212w013w114w215w216w017w118w223w028w151w255w357w458w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
16 touches
28 conflicts
0xe2307994…acad
0x34b655…2a6f
14 touches
21 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
14 touches
21 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
14 touches
21 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
14 touches
21 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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity