← previous blocknext block →recent activity
Analyzing
Block #83,642,703
62 transactions · 47 stateful · 2026-06-25 17:11:13 UTC
Parallelism
61/100
Blocked
83%
Avg conflicts / tx
5.11
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #83,642,703 · 62 txs across 24 waves · depth 24
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
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w414w515w616w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
42 touches
210 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xf324b405…ca30
0x34b655…2a6f
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
14 touches
21 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
210 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity