← previous blocknext block →recent activity
Analyzing
Block #82,975,923
35 transactions · 30 stateful · 2026-06-22 14:56:18 UTC
Parallelism
51/100
Blocked
73%
Avg conflicts / tx
3.26
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #82,975,923 · 35 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w38w09w110w211w312w413w514w615w716w817w918w1019w1120w1221w1323w225w133w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
28 touches
91 conflicts
0x96047c45…b64a
0x34b655…2a6f
12 touches
15 conflicts
0x87fd591e…94fa
0x34b655…2a6f
10 touches
10 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
10 touches
10 conflicts
0x36a49c16…89b9
0xc8689a…ee79
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfcb9138a…3830
0xc8689a…ee79
8 touches
6 conflicts
0x5d537073…cf27
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
91 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity