← previous blocknext block →recent activity
Analyzing
Block #83,666,923
23 transactions · 21 stateful · 2026-06-25 19:52:44 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,666,923 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w28w39w410w511w612w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c6e179…a103
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
14 touches
21 conflicts
0x5176765f…9af2
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x1175233a…64e7
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xdf37a93d…879b
0x34b655…2a6f
12 touches
15 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 0xa0c6e1796c…01a103
Audit this contract →
← previous block·next block →recent activity