← previous blocknext block →recent activity
Analyzing
Block #83,632,679
65 transactions · 46 stateful · 2026-06-25 16:04:15 UTC
Parallelism
62/100
Blocked
78%
Avg conflicts / tx
4.28
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #83,632,679 · 65 txs across 25 waves · depth 25
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
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w19w110w211w312w413w514w615w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
42 touches
210 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
22 touches
55 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
18 touches
36 conflicts
0xe02484a6…c32e
0xc8689a…ee79
18 touches
36 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
18 touches
36 conflicts
0x5396d712…a139
0x34b655…2a6f
16 touches
28 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 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
210 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity