← previous blocknext block →recent activity
Analyzing
Block #83,669,675
21 transactions · 17 stateful · 2026-06-25 20:11:07 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,669,675 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w110w211w312w414w517w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99ee776a…053a
0x34b655…2a6f
8 touches
6 conflicts
0x0f068b13…fb19
0x34b655…2a6f
8 touches
6 conflicts
0x88636b04…3d7a
0x34b655…2a6f
6 touches
3 conflicts
0x529110cf…1128
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x60872583…6452
0x34b655…2a6f
4 touches
1 conflict
0x65df2980…8edc
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x99ee776a78…65053a
Audit this contract →
← previous block·next block →recent activity