← previous blocknext block →recent activity
Analyzing
Block #83,652,324
20 transactions · 20 stateful · 2026-06-25 18:15:28 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,652,324 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w27w38w49w510w613w114w315w418w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x46d5a052…ff2e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x75cdffd8…c217
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
10 conflicts on slot 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity