← previous blocknext block →recent activity
Analyzing
Block #83,617,384
41 transactions · 32 stateful · 2026-06-25 14:22:01 UTC
Parallelism
63/100
Blocked
66%
Avg conflicts / tx
2.07
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,617,384 · 41 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w111w012w113w416w019w120w221w322w423w524w631w1036w1137w1238w1339w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x98d3fc79…df78
0x34b655…2a6f
12 touches
15 conflicts
0xc1740e8f…df93
0xd32edf…ff58
9 touches
10 conflicts
0xd7add284…8d28
0x34b655…2a6f
9 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x0a6cb118…4ca6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x1ec597f9…7c2d
0x34b655…2a6f
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity