← previous blocknext block →recent activity
Analyzing
Block #86,854,828
48 transactions · 42 stateful · 2026-07-10 14:17:18 UTC
Parallelism
63/100
Blocked
79%
Avg conflicts / tx
3.67
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,854,828 · 48 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
1w02w15w06w17w28w39w010w111w212w313w414w515w636w337w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
22 touches
55 conflicts
0x0682a731…d1e7
0x34b655…2a6f
18 touches
36 conflicts
0x0921c970…9f93
0x34b655…2a6f
18 touches
36 conflicts
0x0d2e2e59…f3a6
0x34b655…2a6f
18 touches
36 conflicts
0x0e4000ee…afb9
0x34b655…2a6f
18 touches
36 conflicts
0x4b598c04…5b3b
0x34b655…2a6f
18 touches
36 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
18 touches
36 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity