← previous blocknext block →recent activity
Analyzing
Block #82,736,259
82 transactions · 60 stateful · 2026-06-21 12:15:09 UTC
Parallelism
79/100
Blocked
77%
Avg conflicts / tx
3.84
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #82,736,259 · 82 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w18w216w319w420w525w427w529w631w733w756w857w958w1059w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
34 touches
136 conflicts
0x84f11824…1a31
0xd32edf…ff58
23 touches
66 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
19 touches
45 conflicts
0x18c07e16…8d22
0x34b655…2a6f
18 touches
36 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
18 touches
36 conflicts
0x7ba3d4ba…d55a
0xc8689a…ee79
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
136 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity