← previous blocknext block →recent activity
Analyzing
Block #83,624,165
36 transactions · 29 stateful · 2026-06-25 15:07:23 UTC
Parallelism
53/100
Blocked
66%
Avg conflicts / tx
2.58
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,624,165 · 36 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
1w02w13w05w17w09w113w014w115w216w317w418w519w620w721w822w923w1024w1132w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0xbbec4dcb…832e
0x34b655…2a6f
18 touches
36 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
16 touches
28 conflicts
0x78661b1d…25fa
0x34b655…2a6f
14 touches
21 conflicts
0x24f8b26c…0861
0x34b655…2a6f
12 touches
15 conflicts
0x75291f8b…3ac0
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