← previous blocknext block →recent activity
Analyzing
Block #83,616,965
45 transactions · 37 stateful · 2026-06-25 14:19:13 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
2.44
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,616,965 · 45 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w211w112w015w216w317w418w021w022w123w224w325w426w543w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0x9c4bf061…1101
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0x487922c6…dbd2
0x34b655…2a6f
14 touches
21 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
14 touches
21 conflicts
0x69813bdd…c3a0
0x34b655…2a6f
12 touches
15 conflicts
0xc7a7ddac…46cf
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
78 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity