← previous blocknext block →recent activity
Analyzing
Block #86,677,914
56 transactions · 45 stateful · 2026-07-09 18:35:22 UTC
Parallelism
73/100
Blocked
69%
Avg conflicts / tx
2.18
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,677,914 · 56 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
1w02w14w29w110w313w014w115w218w319w020w121w223w024w125w226w327w430w531w640w342w145w446w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x503b3a72…f6df
0x34b655…2a6f
14 touches
21 conflicts
0x459573ed…fbbe
0x34b655…2a6f
12 touches
15 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe3321cb6…26de
0x34b655…2a6f
8 touches
6 conflicts
0xe5f37cf1…392c
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
8 touches
6 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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity