← previous blocknext block →recent activity
Analyzing
Block #87,168,150
71 transactions · 52 stateful · 2026-07-12 01:10:54 UTC
Parallelism
68/100
Blocked
85%
Avg conflicts / tx
4.23
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,168,150 · 71 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
1w02w13w24w315w116w317w419w520w521w622w623w760w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
38 touches
171 conflicts
0x3230277c…ef39
0xc8689a…ee79
14 touches
21 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
14 touches
21 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
14 touches
21 conflicts
0x25e3730b…24a9
0x34b655…2a6f
14 touches
21 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc7cda03f…b9da
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
171 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity