← previous blocknext block →recent activity
Analyzing
Block #82,965,962
54 transactions · 40 stateful · 2026-06-22 13:49:40 UTC
Parallelism
65/100
Blocked
78%
Avg conflicts / tx
3.74
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #82,965,962 · 54 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
1w02w16w07w18w210w312w415w516w619w020w121w222w341w644w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
38 touches
171 conflicts
0xb8a785a6…c5d1
0x34b655…2a6f
22 touches
55 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
22 touches
55 conflicts
0x7ba3d4ba…d55a
0xc8689a…ee79
22 touches
55 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
12 touches
15 conflicts
0xfcb9138a…3830
0xc8689a…ee79
10 touches
10 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
10 touches
10 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
171 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity