← previous blocknext block →recent activity
Analyzing
Block #83,636,193
33 transactions · 31 stateful · 2026-06-25 16:27:44 UTC
Parallelism
58/100
Blocked
77%
Avg conflicts / tx
2.64
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,636,193 · 33 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
1w02w13w14w25w06w07w18w011w112w113w214w315w416w519w120w321w522w423w524w626w727w829w1030w1131w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f7f1a44…eeeb
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x785889c9…0603
0x34b655…2a6f
10 touches
10 conflicts
0xe4f71034…bb7d
0xd32edf…ff58
9 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x95cb8e34…5eba
0x34b655…2a6f
8 touches
6 conflicts
0x9ad4d28a…c788
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
28 conflicts on slot 0x2f7f1a44b5…3beeeb
Audit this contract →
← previous block·next block →recent activity