← previous blocknext block →recent activity
Analyzing
Block #83,655,199
20 transactions · 17 stateful · 2026-06-25 18:34:35 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,655,199 · 20 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
4w05w16w07w28w39w410w514w015w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf86f15cd…38af
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xb1513a5d…3d40
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x487922c6…dbd2
0x34b655…2a6f
6 touches
3 conflicts
0xb6b7c45d…9d5a
0x34b655…2a6f
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
6 conflicts on slot 0xf86f15cdfb…b938af
Audit this contract →
← previous block·next block →recent activity