pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,669,597
← previous block
next block →
recent activity
Analyzing
Block #83,669,597
9 transactions · 8 stateful · 2026-06-25 20:10:36 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,669,597
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 3
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
setData
#3
execOrders
#4
0x5a5d9a99
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99ee776a…053a
0x34b655…2a6f
6 touches
3 conflicts
0x0f068b13…fb19
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x83c94aa3…aa40
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x0c8b11e0…f347
0x065c9d…c394
2 touches
0 conflicts
0x1549d8f6…6c6d
0x065c9d…c394
2 touches
0 conflicts
0x2682001f…93c4
0x065c9d…c394
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
0x99ee776a78…65053a
Audit this contract →
← previous block
·
next block →
recent activity