← previous blocknext block →recent activity
Analyzing
Block #83,636,648
26 transactions · 23 stateful · 2026-06-25 16:30:47 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,636,648 · 26 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
1w04w05w16w07w18w09w111w012w113w218w019w122w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c320a0…b4a8
0x34b655…2a6f
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0xf4b4898d…f948
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe2be5b72…9ada
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 0x99c320a0a0…feb4a8
Audit this contract →
← previous block·next block →recent activity