← previous blocknext block →recent activity
Analyzing
Block #83,843,438
68 transactions · 61 stateful · 2026-06-26 15:30:34 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
3.63
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,843,438 · 68 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w939w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
22 touches
55 conflicts
0x4ab9f1d1…3563
0xd32edf…ff58
21 touches
55 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0x326a02b5…8dad
0x34b655…2a6f
20 touches
45 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
14 touches
21 conflicts
0xc13fac9b…d2d5
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity