← previous blocknext block →recent activity
Analyzing
Block #83,614,577
63 transactions · 47 stateful · 2026-06-25 14:03:14 UTC
Parallelism
60/100
Blocked
85%
Avg conflicts / tx
5.78
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #83,614,577 · 63 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
1w02w13w216w317w419w521w622w725w826w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
48 touches
276 conflicts
0x0cdf9369…5331
0x34b655…2a6f
20 touches
45 conflicts
0x29620e65…611e
0xd32edf…ff58
19 touches
45 conflicts
0x5941ac48…c525
0x34b655…2a6f
18 touches
36 conflicts
0x2484cc15…5afc
0x34b655…2a6f
18 touches
36 conflicts
0xe02484a6…c32e
0xc8689a…ee79
18 touches
36 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
16 touches
28 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
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
276 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity