← previous blocknext block →recent activity
Analyzing
Block #83,614,758
43 transactions · 36 stateful · 2026-06-25 14:04:27 UTC
Parallelism
63/100
Blocked
64%
Avg conflicts / tx
2.7
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,614,758 · 43 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w09w110w411w512w013w114w215w316w417w518w619w720w821w922w1023w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x9e4890bd…fd9d
0x34b655…2a6f
14 touches
21 conflicts
0x8e507257…71c1
0x34b655…2a6f
12 touches
15 conflicts
0xeeaac7c3…90f0
0x34b655…2a6f
12 touches
15 conflicts
0xd1c9e546…426d
0x34b655…2a6f
12 touches
15 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 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
78 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity