pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,844,754
← previous block
next block →
recent activity
Analyzing
Block #97,844,754
10 transactions · 10 stateful · 2026-08-21 07:04:48 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,844,754
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrder
· blocks 1
#3
execPerpOps
· blocks 1
#6
0xaf47a8bb
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x59558d29
#4
execPerpOps
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x10cc9469…5b6c
0x34b655…2a6f
2 touches
0 conflicts
0x17ce7874…0569
0x34b655…2a6f
2 touches
0 conflicts
0x1a979328…3f6a
0x34b655…2a6f
2 touches
0 conflicts
0x1ba33c52…2015
0x34b655…2a6f
2 touches
0 conflicts
0x2da03d4e…e374
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity