← previous blocknext block →recent activity
Analyzing
Block #86,487,270
34 transactions · 32 stateful · 2026-07-08 21:18:48 UTC
Parallelism
47/100
Blocked
56%
Avg conflicts / tx
3.91
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,487,270 · 34 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
1w02w13w04w25w36w47w58w69w710w811w912w1013w1114w1215w1318w525w1430w1632w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
26 touches
78 conflicts
0x922c7ebd…6600
0xc8689a…ee79
24 touches
66 conflicts
0x9f40a209…1193
0x34b655…2a6f
24 touches
66 conflicts
0xa7e2f1b7…7e6f
0x34b655…2a6f
22 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xb9bc1dfc…6bfb
0x34b655…2a6f
14 touches
21 conflicts
0xe727ab72…768b
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity