← previous blocknext block →recent activity
Analyzing
Block #83,627,080
16 transactions · 15 stateful · 2026-06-25 15:26:50 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,627,080 · 16 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
1w04w15w06w19w010w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6632320…a3ce
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e2262…cd8c
0x34b655…2a6f
6 touches
3 conflicts
0x55210543…1d06
0x34b655…2a6f
4 touches
1 conflict
0x62435729…b454
0x34b655…2a6f
4 touches
1 conflict
0x70109235…1f74
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
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 0xb6632320a3…16a3ce
Audit this contract →
← previous block·next block →recent activity