← previous blocknext block →recent activity
Analyzing
Block #83,636,765
20 transactions · 16 stateful · 2026-06-25 16:31:34 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,636,765 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w011w112w213w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23bcb6e8…566e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xf4b4898d…f948
0x34b655…2a6f
6 touches
3 conflicts
0x14fd38f5…fdbb
0x34b655…2a6f
4 touches
1 conflict
0x811cb01f…e507
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
6 conflicts on slot 0x23bcb6e83b…19566e
Audit this contract →
← previous block·next block →recent activity