pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,654,414
← previous block
next block →
recent activity
Analyzing
Block #96,654,414
9 transactions · 8 stateful · 2026-08-17 02:16:32 UTC
Parallelism
67
/100
Blocked
38
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,654,414
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execPerpOps
#5
0x3f5c179b
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#3
execFwdPositionOpsV2
· blocks 1
#6
batchUpdate
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0x54526994…55b2
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x8c118f21…20fe
0x34b655…2a6f
4 touches
1 conflict
0xa4626144…664f
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0xf118688e…cb4c
0x34b655…2a6f
4 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:
0x851145ea…9f3f07
1 conflict on slot
0xc73fd5491a…292e28
Audit this contract →
← previous block
·
next block →
recent activity