← previous blocknext block →recent activity
Analyzing
Block #86,622,192
43 transactions · 37 stateful · 2026-07-09 12:21:58 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2.7
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,622,192 · 43 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w28w39w010w111w213w014w115w216w317w418w519w620w721w822w924w327w330w435w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x87ee379a…cd9e
0x34b655…2a6f
10 touches
10 conflicts
0xca2926e0…61b5
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa29182a1…c12c
0x34b655…2a6f
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity