← previous blocknext block →recent activity
Analyzing
Block #83,412,266
19 transactions · 17 stateful · 2026-06-24 15:33:13 UTC
Parallelism
58/100
Blocked
41%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,412,266 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w411w513w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xbbec4dcb…832e
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xdf37a93d…879b
0x34b655…2a6f
10 touches
10 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
10 touches
10 conflicts
0x5d2b5661…df66
0x34b655…2a6f
9 touches
10 conflicts
0x2004b5f1…ff98
0x34b655…2a6f
8 touches
10 conflicts
0x264f234b…3bc2
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
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity