pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,609,859
← previous block
next block →
recent activity
Analyzing
Block #96,609,859
9 transactions · 9 stateful · 2026-08-16 22:32:28 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,609,859
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xa7481e1f…531f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd16f9ba4…8b05
0x34b655…2a6f
4 touches
1 conflict
0xd7e4217d…7c6b
0x34b655…2a6f
4 touches
1 conflict
0x9ff94a68…7ae8
0x34b655…2a6f
3 touches
1 conflict
0x7fd55c5f…1f35
0x34b655…2a6f
3 touches
1 conflict
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
0xf9874e3690…90beed
Audit this contract →
← previous block
·
next block →
recent activity