← previous blocknext block →recent activity
Analyzing
Block #83,639,109
18 transactions · 17 stateful · 2026-06-25 16:47:12 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,639,109 · 18 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
3w04w16w27w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x37a276a3…673f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x2df95183…dbda
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfa032…139c
0x34b655…2a6f
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
2 touches
0 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
3 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity