← previous blocknext block →recent activity
Analyzing
Block #83,398,134
30 transactions · 24 stateful · 2026-06-24 13:58:46 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,398,134 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w39w410w011w112w213w314w415w517w618w726w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7d68b808…c6e3
0x34b655…2a6f
8 touches
6 conflicts
0xb6632320…a3ce
0x34b655…2a6f
8 touches
6 conflicts
0x577441b7…43ff
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x84611dd3…b347
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity