← previous blocknext block →recent activity
Analyzing
Block #83,633,527
70 transactions · 48 stateful · 2026-06-25 16:09:55 UTC
Parallelism
66/100
Blocked
79%
Avg conflicts / tx
3.54
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #83,633,527 · 70 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
1w02w04w17w18w011w112w213w314w415w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
38 touches
171 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 conflicts
0xd79c9727…1233
0x34b655…2a6f
16 touches
28 conflicts
0x6ebd33e0…a9de
0x34b655…2a6f
16 touches
28 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
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
171 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity