← previous blocknext block →recent activity
Analyzing
Block #82,968,816
41 transactions · 33 stateful · 2026-06-22 14:08:45 UTC
Parallelism
66/100
Blocked
73%
Avg conflicts / tx
2.34
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #82,968,816 · 41 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w05w06w17w29w210w311w412w115w016w117w218w319w420w521w622w323w429w531w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0x08913286…f0df
0x34b655…2a6f
16 touches
28 conflicts
0x8672c4d6…675c
0x34b655…2a6f
12 touches
15 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0f21840f…6cde
0x34b655…2a6f
10 touches
10 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
8 touches
6 conflicts
0xbd7e0241…07f5
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity