← previous blocknext block →recent activity
Analyzing
Block #84,352,172
30 transactions · 23 stateful · 2026-06-29 00:00:05 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,352,172 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w112w214w315w423w025w127w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x5f3fc680…f989
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xcffc17bc…3544
0x34b655…2a6f
6 touches
3 conflicts
0x753da1ce…6bbd
0x34b655…2a6f
6 touches
3 conflicts
0x64e19ce5…8a52
0xd32edf…ff58
5 touches
3 conflicts
0x8fcf2308…746e
0x34b655…2a6f
5 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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity