← previous blocknext block →recent activity
Analyzing
Block #83,629,716
22 transactions · 17 stateful · 2026-06-25 15:44:27 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,629,716 · 22 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
3w05w19w010w111w212w314w017w118w220w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacb576ad…e0a1
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
6 touches
3 conflicts
0x5396d712…a139
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xda337bea…f20a
0xd32edf…ff58
5 touches
3 conflicts
0x057101ce…1647
0x34b655…2a6f
4 touches
1 conflict
0x5e6812fc…74fe
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 0xacb576ad50…3fe0a1
Audit this contract →
← previous block·next block →recent activity