← previous blocknext block →recent activity
Analyzing
Block #85,132,131
44 transactions · 38 stateful · 2026-07-02 14:42:24 UTC
Parallelism
66/100
Blocked
74%
Avg conflicts / tx
2.68
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #85,132,131 · 44 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w110w011w112w013w114w215w316w417w518w619w720w821w922w1023w1128w229w131w332w434w140w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xc3c7cf34…43da
0x34b655…2a6f
16 touches
28 conflicts
0xe47478a3…a058
0x34b655…2a6f
16 touches
28 conflicts
0x7ae63663…9d94
0x34b655…2a6f
16 touches
28 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
16 touches
28 conflicts
0x97c67486…27fe
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0xd98b3c10…67b8
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity