← previous blocknext block →recent activity
Analyzing
Block #86,711,449
53 transactions · 50 stateful · 2026-07-09 22:19:08 UTC
Parallelism
62/100
Blocked
70%
Avg conflicts / tx
4.38
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,711,449 · 53 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
1w02w03w04w17w09w110w212w313w414w515w016w143w144w645w247w448w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
38 touches
171 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x63c900f4…2600
0x34b655…2a6f
14 touches
21 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x5b6af007…0f35
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
171 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity