← previous blocknext block →recent activity
Analyzing
Block #83,670,622
25 transactions · 22 stateful · 2026-06-25 20:17:25 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,670,622 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w211w312w413w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cf1f868…c5af
0x34b655…2a6f
14 touches
21 conflicts
0x13c5b486…d41e
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x65df2980…8edc
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xd4702f73…926c
0x34b655…2a6f
8 touches
6 conflicts
0xed1add2a…2d6a
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 0x8cf1f86890…38c5af
Audit this contract →
← previous block·next block →recent activity