← previous blocknext block →recent activity
Analyzing
Block #83,635,209
9 transactions · 9 stateful · 2026-06-25 16:21:10 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,635,209 · 9 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
2w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x505f101e…7ad6
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x125c5027…eb59
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
2 touches
0 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
2 touches
0 conflicts
0xab1d8e20…4f23
0x34b655…2a6f
2 touches
0 conflicts
0xc9493039…ea3b
0x34b655…2a6f
2 touches
0 conflicts
0xd3d708df…612c
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 0x505f101e7e…6e7ad6
Audit this contract →
← previous block·next block →recent activity