← previous blocknext block →recent activity
Analyzing
Block #83,632,136
53 transactions · 35 stateful · 2026-06-25 16:00:37 UTC
Parallelism
59/100
Blocked
80%
Avg conflicts / tx
3.55
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #83,632,136 · 53 txs across 22 waves · depth 22
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w514w322w023w124w225w326w427w528w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
34 touches
136 conflicts
0x022f72c3…07b6
0xc8689a…ee79
18 touches
36 conflicts
0x1d4b0baf…1423
0x34b655…2a6f
18 touches
36 conflicts
0x5396d712…a139
0x34b655…2a6f
18 touches
36 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
18 touches
36 conflicts
0xd53220ed…4737
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
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