← previous blocknext block →recent activity
Analyzing
Block #83,616,555
41 transactions · 32 stateful · 2026-06-25 14:16:28 UTC
Parallelism
56/100
Blocked
72%
Avg conflicts / tx
2.93
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,616,555 · 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
1w02w13w28w39w411w513w014w115w216w319w420w521w622w723w824w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0xc3464910…786f
0x34b655…2a6f
16 touches
28 conflicts
0x2484cc15…5afc
0x34b655…2a6f
14 touches
21 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0x5941ac48…c525
0x34b655…2a6f
14 touches
21 conflicts
0x27d953f7…88a3
0xd32edf…ff58
11 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 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