← previous blocknext block →recent activity
Analyzing
Block #83,400,714
243 transactions · 40 stateful · 2026-06-24 14:16:02 UTC
Parallelism
93/100
Blocked
70%
Avg conflicts / tx
0.65
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,400,714 · 243 txs across 18 waves · depth 18
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
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w023w047w160w284w3106w4126w5145w6222w1228w4230w5231w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
24 touches
66 conflicts
0x8e507257…71c1
0x34b655…2a6f
20 touches
45 conflicts
0xa457c06e…2f06
0x34b655…2a6f
20 touches
45 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0xffc2f21e…b393
0x34b655…2a6f
14 touches
21 conflicts
0xf5f29db8…11a3
0x34b655…2a6f
14 touches
21 conflicts
0x5811d761…a34b
0xd32edf…ff58
13 touches
21 conflicts
0x60d07066…695c
0x34b655…2a6f
12 touches
15 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
66 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity