← previous blocknext block →recent activity
Analyzing
Block #83,614,576
44 transactions · 39 stateful · 2026-06-25 14:03:14 UTC
Parallelism
61/100
Blocked
64%
Avg conflicts / tx
3.18
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,614,576 · 44 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
1w03w04w16w17w29w310w411w519w020w121w222w323w424w525w626w727w828w929w1030w1131w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0x5941ac48…c525
0x34b655…2a6f
10 touches
10 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
10 touches
10 conflicts
0xc3464910…786f
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
10 touches
10 conflicts
0xeeaac7c3…90f0
0x34b655…2a6f
10 touches
10 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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity