← previous blocknext block →recent activity
Analyzing
Block #83,668,687
15 transactions · 14 stateful · 2026-06-25 20:04:32 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,668,687 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w19w210w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c6b2fa…098d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf17589f…048c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8f4c5cb2…cbee
0x34b655…2a6f
4 touches
1 conflict
0xb98f6ee1…f475
0x34b655…2a6f
4 touches
1 conflict
0x830a292d…70f6
0x40c49f…2af0
2 touches
0 conflicts
0xb0d58cc9…8d90
0x40c49f…2af0
2 touches
0 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
3 conflicts on slot 0x68c6b2fafb…86098d
Audit this contract →
← previous block·next block →recent activity