← previous blocknext block →recent activity
Analyzing
Block #83,630,402
50 transactions · 35 stateful · 2026-06-25 15:49:01 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.82
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,630,402 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w29w210w311w412w513w614w738w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0xbe96eab4…b767
0xd32edf…ff58
17 touches
36 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
14 touches
21 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity