← previous blocknext block →recent activity
Analyzing
Block #83,617,281
56 transactions · 44 stateful · 2026-06-25 14:21:20 UTC
Parallelism
68/100
Blocked
77%
Avg conflicts / tx
3.57
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,617,281 · 56 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
5w09w012w113w214w315w416w517w618w738w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…003d
0x40c49f…2af0
16 touches
28 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
14 touches
21 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
12 touches
15 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
12 touches
15 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
12 touches
15 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
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