← previous blocknext block →recent activity
Analyzing
Block #83,673,073
13 transactions · 12 stateful · 2026-06-25 20:33:44 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,673,073 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w19w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571cb36d…3b3d
0x34b655…2a6f
10 touches
10 conflicts
0x1175233a…64e7
0x34b655…2a6f
8 touches
6 conflicts
0x225520de…81ba
0x34b655…2a6f
8 touches
6 conflicts
0x5176765f…9af2
0x34b655…2a6f
6 touches
3 conflicts
0x7a30c0d5…a314
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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 0x571cb36db3…a33b3d
Audit this contract →
← previous block·next block →recent activity