← previous blocknext block →recent activity
Analyzing
Block #83,615,868
61 transactions · 47 stateful · 2026-06-25 14:11:52 UTC
Parallelism
69/100
Blocked
81%
Avg conflicts / tx
3.33
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,615,868 · 61 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w19w210w313w116w217w338w439w244w345w446w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0xffc2f21e…b393
0x34b655…2a6f
16 touches
28 conflicts
0x487922c6…dbd2
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
16 touches
28 conflicts
0xc2ab3ad1…a6bc
0x34b655…2a6f
13 touches
26 conflicts
0x921d6415…b6ca
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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity