← previous blocknext block →recent activity
Analyzing
Block #83,665,051
34 transactions · 34 stateful · 2026-06-25 19:40:14 UTC
Parallelism
56/100
Blocked
65%
Avg conflicts / tx
3.06
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,665,051 · 34 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w18w09w110w011w114w115w016w117w218w319w420w521w622w723w824w927w230w1232w1333w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0xcc2cd268…5687
0x34b655…2a6f
14 touches
21 conflicts
0x157dbfb2…4089
0x34b655…2a6f
10 touches
10 conflicts
0x06571461…d6f0
0x34b655…2a6f
10 touches
10 conflicts
0x6b47245e…a342
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xe64e6363…e676
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity