← previous blocknext block →recent activity
Analyzing
Block #83,854,050
33 transactions · 31 stateful · 2026-06-26 16:41:22 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,854,050 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w48w59w010w111w212w313w414w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xd637b3…4160
12 touches
15 conflicts
0xc4232e9d…dc6a
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xd5b10148…e638
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x6f6fc26c…3e34
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity