← previous blocknext block →recent activity
Analyzing
Block #82,966,281
28 transactions · 20 stateful · 2026-06-22 13:51:48 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.5
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #82,966,281 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w717w123w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0xbd7e0241…07f5
0x34b655…2a6f
10 touches
10 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
10 touches
10 conflicts
0x36a49c16…89b9
0xc8689a…ee79
10 touches
10 conflicts
0x570f5a01…28a4
0x34b655…2a6f
8 touches
9 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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
28 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity