← previous blocknext block →recent activity
Analyzing
Block #82,965,894
26 transactions · 19 stateful · 2026-06-22 13:49:13 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,965,894 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w29w010w111w212w313w222w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
10 touches
10 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0xfcb9138a…3830
0xc8689a…ee79
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x9cd748ec…4160
0x34b655…2a6f
6 touches
3 conflicts
0xab83f300…f8c8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x89750670…2dea
0xa6afd3…d132
6 touches
3 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
10 conflicts on slot 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity