← previous blocknext block →recent activity
Analyzing
Block #83,456,177
39 transactions · 35 stateful · 2026-06-24 20:26:35 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
2.64
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,456,177 · 39 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
1w05w16w27w38w012w113w214w315w417w618w719w820w921w1022w1123w1225w428w138w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x022f72c3…07b6
0xc8689a…ee79
20 touches
45 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
18 touches
36 conflicts
0xdf37a93d…879b
0x34b655…2a6f
18 touches
36 conflicts
0x2f7f1a44…eeeb
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x126a0344…4465
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity