← previous blocknext block →recent activity
Analyzing
Block #82,341,619
78 transactions · 59 stateful · 2026-06-19 16:18:22 UTC
Parallelism
69/100
Blocked
78%
Avg conflicts / tx
4.31
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #82,341,619 · 78 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
1w02w13w24w35w46w57w68w79w810w927w1029w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
38 touches
171 conflicts
0x08913286…f0df
0x34b655…2a6f
26 touches
78 conflicts
0xdfd3a9ef…2a0b
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…00c9
0x34b655…2a6f
20 touches
45 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x463be44a…2830
0x34b655…2a6f
15 touches
28 conflicts
0xab83f300…f8c8
0x34b655…2a6f
14 touches
21 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity