← previous blocknext block →recent activity
Analyzing
Block #83,482,334
41 transactions · 35 stateful · 2026-06-24 23:21:07 UTC
Parallelism
56/100
Blocked
71%
Avg conflicts / tx
4.95
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,482,334 · 41 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w211w012w113w214w315w416w517w618w719w820w921w1022w1123w1224w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
30 touches
105 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0xffc2f21e…b393
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x326a02b5…8dad
0x34b655…2a6f
18 touches
36 conflicts
0x97c67486…27fe
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0x18cbab19…7a73
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
105 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity