← previous blocknext block →recent activity
Analyzing
Block #83,642,688
23 transactions · 21 stateful · 2026-06-25 17:11:07 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,642,688 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w210w311w412w513w616w017w219w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc8dd43…8cf2
0x34b655…2a6f
12 touches
15 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x6ca8bab1…3957
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
6 touches
3 conflicts
0x59d40d96…58a4
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
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
15 conflicts on slot 0x5cc8dd430f…428cf2
Audit this contract →
← previous block·next block →recent activity