← previous blocknext block →recent activity
Analyzing
Block #83,652,120
30 transactions · 26 stateful · 2026-06-25 18:14:06 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,652,120 · 30 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
1w04w15w27w39w010w113w214w315w416w517w620w427w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c53a187…3646
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x6ab4f016…51bb
0xd32edf…ff58
9 touches
10 conflicts
0x3139c500…6dca
0x34b655…2a6f
8 touches
6 conflicts
0xa0c6e179…a103
0x34b655…2a6f
8 touches
6 conflicts
0xfbf0b409…2ac6
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 0x2c53a187ea…bc3646
Audit this contract →
← previous block·next block →recent activity