← previous blocknext block →recent activity
Analyzing
Block #83,628,500
79 transactions · 50 stateful · 2026-06-25 15:36:20 UTC
Parallelism
71/100
Blocked
82%
Avg conflicts / tx
3.48
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #83,628,500 · 79 txs across 23 waves · depth 23
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
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w216w318w419w522w524w662w763w864w965w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
36 touches
153 conflicts
0xfe05e125…e11c
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001b
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002b
0x1b6862…e19c
16 touches
28 conflicts
0x91220b8f…7a04
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x75291f8b…3ac0
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
153 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity