← previous blocknext block →recent activity
Analyzing
Block #83,398,674
85 transactions · 71 stateful · 2026-06-24 14:02:23 UTC
Parallelism
75/100
Blocked
83%
Avg conflicts / tx
5.11
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,398,674 · 85 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
1w02w13w24w35w46w57w68w79w810w911w1012w1124w227w330w1232w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
38 touches
171 conflicts
0x0642bda6…ba0c
0xd32edf…ff58
27 touches
91 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
26 touches
78 conflicts
0x00000000…001e
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…002e
0x1b6862…e19c
22 touches
55 conflicts
0x3a3097d7…2ab8
0x1b6862…e19c
22 touches
55 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
22 touches
55 conflicts
0x00000000…0012
0x1b6862…e19c
22 touches
55 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