← previous blocknext block →recent activity
Analyzing
Block #83,617,161
41 transactions · 33 stateful · 2026-06-25 14:20:31 UTC
Parallelism
59/100
Blocked
70%
Avg conflicts / tx
3.41
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,617,161 · 41 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w29w011w112w215w016w117w218w319w420w521w622w723w824w925w1026w1127w1228w1329w1430w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0xdf37a93d…879b
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0xc2ab3ad1…a6bc
0x34b655…2a6f
16 touches
28 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
16 touches
28 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
16 touches
28 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
16 touches
28 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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity