← previous blocknext block →recent activity
Analyzing
Block #87,063,622
53 transactions · 39 stateful · 2026-07-11 13:32:41 UTC
Parallelism
66/100
Blocked
79%
Avg conflicts / tx
3.4
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,063,622 · 53 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w110w114w215w316w417w218w320w421w523w624w325w446w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0x43ffd8bd…0d0c
0x34b655…2a6f
20 touches
45 conflicts
0x2484cc15…5afc
0x34b655…2a6f
20 touches
45 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
20 touches
45 conflicts
0x3413a430…234a
0x34b655…2a6f
20 touches
45 conflicts
0x79fade94…7f93
0x34b655…2a6f
20 touches
45 conflicts
0x7b3da897…b268
0x34b655…2a6f
20 touches
45 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