← previous blocknext block →recent activity
Analyzing
Block #83,670,827
13 transactions · 13 stateful · 2026-06-25 20:18:48 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,670,827 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w28w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13c5b486…d41e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xcb3e7bf5…8ae6
0x34b655…2a6f
4 touches
1 conflict
0xd3910982…d035
0x34b655…2a6f
4 touches
1 conflict
0x17920e20…8655
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
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 0x13c5b4868d…1ad41e
Audit this contract →
← previous block·next block →recent activity