← previous blocknext block →recent activity
Analyzing
Block #83,637,032
31 transactions · 24 stateful · 2026-06-25 16:33:21 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.55
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,637,032 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w09w115w216w317w418w519w620w725w729w830w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf997c4c7…617d
0x34b655…2a6f
18 touches
36 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
10 touches
10 conflicts
0x1018dbda…b4df
0x34b655…2a6f
10 touches
10 conflicts
0x619f5683…5bd4
0x34b655…2a6f
8 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
36 conflicts on slot 0xf997c4c76f…f2617d
Audit this contract →
← previous block·next block →recent activity