← previous blocknext block →recent activity
Analyzing
Block #83,668,011
34 transactions · 30 stateful · 2026-06-25 20:00:01 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,668,011 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w210w011w012w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xcb4784d8…e866
0x34b655…2a6f
12 touches
15 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
12 touches
15 conflicts
0x4467ecee…e95b
0x34b655…2a6f
12 touches
15 conflicts
0xdf37a93d…879b
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0x6bcc630d…6787
0xd32edf…ff58
7 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity