← previous blocknext block →recent activity
Analyzing
Block #83,637,046
21 transactions · 16 stateful · 2026-06-25 16:33:27 UTC
Parallelism
62/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,637,046 · 21 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
1w09w110w212w313w414w517w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4580b7bd…34f3
0x34b655…2a6f
10 touches
10 conflicts
0x5cc8dd43…8cf2
0x34b655…2a6f
10 touches
10 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x1018dbda…b4df
0x34b655…2a6f
6 touches
3 conflicts
0x20e499f7…fa84
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x4580b7bdd0…5b34f3
Audit this contract →
← previous block·next block →recent activity