← previous blocknext block →recent activity
Analyzing
Block #82,965,530
65 transactions · 51 stateful · 2026-06-22 13:46:47 UTC
Parallelism
71/100
Blocked
78%
Avg conflicts / tx
3.74
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #82,965,530 · 65 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w08w09w110w011w112w214w316w417w519w622w742w743w844w645w850w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
32 touches
120 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x3a6290da…e683
0x34b655…2a6f
16 touches
28 conflicts
0xfcb9138a…3830
0xc8689a…ee79
14 touches
21 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0xab83f300…f8c8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
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
120 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity