← previous blocknext block →recent activity
Analyzing
Block #82,965,950
55 transactions · 47 stateful · 2026-06-22 13:49:35 UTC
Parallelism
64/100
Blocked
79%
Avg conflicts / tx
4.25
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #82,965,950 · 55 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w18w210w111w012w113w314w215w316w217w418w519w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
40 touches
190 conflicts
0x7ba3d4ba…d55a
0xc8689a…ee79
20 touches
45 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
20 touches
45 conflicts
0xb8a785a6…c5d1
0x34b655…2a6f
20 touches
45 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
16 touches
28 conflicts
0xab83f300…f8c8
0x34b655…2a6f
16 touches
28 conflicts
0xfcb9138a…3830
0xc8689a…ee79
16 touches
28 conflicts
0xc3688185…9b36
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 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity