← previous blocknext block →recent activity
Analyzing
Block #83,618,362
64 transactions · 53 stateful · 2026-06-25 14:28:34 UTC
Parallelism
64/100
Blocked
79%
Avg conflicts / tx
4.81
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #83,618,362 · 64 txs across 23 waves · depth 23
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w514w215w618w719w720w821w822w949w950w1051w1152w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
38 touches
171 conflicts
0x0ddda70e…a9c5
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…001b
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002b
0x1b6862…e19c
20 touches
45 conflicts
0x98067f20…59e6
0x1b6862…e19c
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 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