← previous blocknext block →recent activity
Analyzing
Block #83,628,579
23 transactions · 22 stateful · 2026-06-25 15:36:52 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,628,579 · 23 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
4w05w16w07w18w29w310w411w516w120w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07a0dea2…ca8c
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
10 touches
10 conflicts
0x6dff5efb…1f00
0x34b655…2a6f
10 touches
10 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
10 touches
10 conflicts
0x75cdffd8…c217
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
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 0x07a0dea248…11ca8c
Audit this contract →
← previous block·next block →recent activity