← previous blocknext block →recent activity
Analyzing
Block #83,666,177
56 transactions · 40 stateful · 2026-06-25 19:47:45 UTC
Parallelism
63/100
Blocked
78%
Avg conflicts / tx
3.16
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,666,177 · 56 txs across 21 waves · depth 21
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
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w09w410w511w622w023w130w231w332w433w550w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
18 touches
36 conflicts
0xdf37a93d…879b
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
14 touches
21 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0x16dce2e7…6f05
0x34b655…2a6f
12 touches
15 conflicts
0x020501e5…da24
0xd32edf…ff58
11 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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity