← previous blocknext block →recent activity
Analyzing
Block #86,911,534
55 transactions · 44 stateful · 2026-07-10 20:36:34 UTC
Parallelism
64/100
Blocked
80%
Avg conflicts / tx
3.44
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,911,534 · 55 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w38w09w110w211w012w114w216w317w418w544w145w246w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
16 touches
28 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
12 touches
15 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
12 touches
15 conflicts
0x9e3c397e…e3a9
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 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