← previous blocknext block →recent activity
Analyzing
Block #83,630,639
32 transactions · 28 stateful · 2026-06-25 15:50:36 UTC
Parallelism
59/100
Blocked
61%
Avg conflicts / tx
1.53
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,630,639 · 32 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w210w011w012w113w214w315w416w517w618w719w825w127w1029w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
8 touches
6 conflicts
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0xdb19247d…233c
0x34b655…2a6f
8 touches
6 conflicts
0x0b408000…9df1
0x34b655…2a6f
6 touches
5 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x23c5c9ed…69bb
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity