← previous blocknext block →recent activity
Analyzing
Block #83,636,542
70 transactions · 52 stateful · 2026-06-25 16:30:04 UTC
Parallelism
70/100
Blocked
81%
Avg conflicts / tx
3.49
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,636,542 · 70 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
1w02w13w24w35w46w57w68w79w810w911w214w215w358w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0x5224f4c0…f627
0xd32edf…ff58
21 touches
55 conflicts
0x7dc64b2c…05e7
0x34b655…2a6f
16 touches
28 conflicts
0xb147eeb0…d658
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0x1f8a126c…9aa4
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity