← previous blocknext block →recent activity
Analyzing
Block #86,619,622
41 transactions · 34 stateful · 2026-07-09 12:04:49 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
2.12
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #86,619,622 · 41 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w29w010w111w212w313w414w516w617w718w819w921w223w324w125w826w227w431w532w538w1039w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
10 touches
10 conflicts
0x9365e097…ff56
0x34b655…2a6f
10 touches
10 conflicts
0xa29182a1…c12c
0x34b655…2a6f
10 touches
10 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
8 touches
6 conflicts
0x64aaadbf…f9f3
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