pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,512,032
← previous block
next block →
recent activity
Analyzing
Block #96,512,032
10 transactions · 8 stateful · 2026-08-16 14:20:25 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,512,032
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execFwdPositionOpsV2
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0x3f5c179b
#8
setData
#9
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0x060b4e83…4f56
0x34b655…2a6f
4 touches
1 conflict
0x8ac41992…cf98
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfe708efe…df34
0x34b655…2a6f
4 touches
1 conflict
0x2bd66f15…8cee
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x48719cbe…5484
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
1 conflict on slot
0x7c93b38ab4…099e69
Audit this contract →
← previous block
·
next block →
recent activity