← previous blocknext block →recent activity
Analyzing
Block #83,639,170
18 transactions · 17 stateful · 2026-06-25 16:47:37 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,639,170 · 18 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
1w02w03w04w16w07w19w110w211w313w414w516w317w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1e51cc8…e4cf
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x049cca71…b102
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x1b1df992…40eb
0x34b655…2a6f
4 touches
1 conflict
0x8ae827f1…aa36
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
3 conflicts on slot 0xa1e51cc8b9…e4e4cf
Audit this contract →
← previous block·next block →recent activity