← previous blocknext block →recent activity
Analyzing
Block #83,616,295
62 transactions · 52 stateful · 2026-06-25 14:14:44 UTC
Parallelism
71/100
Blocked
77%
Avg conflicts / tx
3.77
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,616,295 · 62 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
1w02w04w06w19w212w315w416w520w644w1147w150w351w452w154w557w1259w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
34 touches
136 conflicts
0x1a56ea55…a3d5
0xd32edf…ff58
15 touches
28 conflicts
0x75cdffd8…c217
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x5941ac48…c525
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x2484cc15…5afc
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
136 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity