← previous blocknext block →recent activity
Analyzing
Block #82,519,901
84 transactions · 64 stateful · 2026-06-20 12:07:42 UTC
Parallelism
73/100
Blocked
80%
Avg conflicts / tx
4.46
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #82,519,901 · 84 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
1w02w13w24w35w46w57w68w79w818w519w622w725w827w929w1030w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
40 touches
190 conflicts
0x89e647e0…2616
0xd32edf…ff58
23 touches
66 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xbc66586e…20fe
0x34b655…2a6f
21 touches
55 conflicts
0x08913286…f0df
0x34b655…2a6f
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 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
190 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity