← previous blocknext block →recent activity
Analyzing
Block #83,625,800
18 transactions · 17 stateful · 2026-06-25 15:18:16 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,625,800 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w111w113w214w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3464910…786f
0x34b655…2a6f
6 touches
3 conflicts
0xff107718…55e9
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xfe2b22b7…5965
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…4737
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x156df99c…8781
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xc346491067…b0786f
Audit this contract →
← previous block·next block →recent activity