pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,609,094
← previous block
next block →
recent activity
Analyzing
Block #96,609,094
9 transactions · 8 stateful · 2026-08-16 22:28:37 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,609,094
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#6
setData
#7
execOrders
#8
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xcbcfd423…748a
0x34b655…2a6f
4 touches
1 conflict
0x364026a6…1715
0x34b655…2a6f
2 touches
0 conflicts
0x3ff58865…cdd3
0x34b655…2a6f
2 touches
0 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
2 touches
0 conflicts
0x5e78c401…7a7e
0x34b655…2a6f
2 touches
0 conflicts
0x9a36cb2e…0929
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
0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block
·
next block →
recent activity