← previous blocknext block →recent activity
Analyzing
Block #86,780,002
40 transactions · 34 stateful · 2026-07-10 05:57:11 UTC
Parallelism
57/100
Blocked
79%
Avg conflicts / tx
2.27
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,780,002 · 40 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
1w02w14w15w26w29w010w111w212w313w414w515w616w717w822w223w324w425w526w133w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x216ffe66…1f94
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x46b62326…9b3c
0xa6afd3…d132
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity