← previous blocknext block →recent activity
Analyzing
Block #83,632,182
17 transactions · 16 stateful · 2026-06-25 16:00:56 UTC
Parallelism
65/100
Blocked
31%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,632,182 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5396d712…a139
0x34b655…2a6f
12 touches
15 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x6ca8bab1…3957
0x34b655…2a6f
10 touches
10 conflicts
0x2b25ee9a…af8c
0x34b655…2a6f
8 touches
6 conflicts
0x2f68b7eb…7386
0x34b655…2a6f
4 touches
1 conflict
0x21c732cc…1e52
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x5396d712af…cba139
Audit this contract →
← previous block·next block →recent activity