← previous blocknext block →recent activity
Analyzing
Block #83,672,960
14 transactions · 11 stateful · 2026-06-25 20:32:58 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,672,960 · 14 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
4w05w16w28w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3115f686…67ee
0x34b655…2a6f
8 touches
6 conflicts
0x9863393c…ce7b
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x674e7fc0…d95f
0x34b655…2a6f
6 touches
3 conflicts
0x688e086a…5f75
0x34b655…2a6f
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x3115f686f7…6167ee
Audit this contract →
← previous block·next block →recent activity