← previous blocknext block →recent activity
Analyzing
Block #83,633,592
32 transactions · 23 stateful · 2026-06-25 16:10:21 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,633,592 · 32 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
5w06w112w015w016w117w018w220w021w222w124w225w127w228w330w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x32329fca…2d8c
0x34b655…2a6f
6 touches
3 conflicts
0x44f25d4e…0960
0xd32edf…ff58
5 touches
3 conflicts
0x1ca68aab…5e4a
0x34b655…2a6f
4 touches
1 conflict
0x1f7b1577…d049
0x34b655…2a6f
4 touches
1 conflict
0x33412db4…0073
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity