pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,550,446
← previous block
next block →
recent activity
Analyzing
Block #95,550,446
10 transactions · 9 stateful · 2026-08-13 05:42:04 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,550,446
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
· blocks 1
#4
batchUpdatePrice
#6
execFwdPositionOps
#7
relay
#8
execFwdPositionOps
#9
setData
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa59e109d…d53b
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xd840c9df…2d85
0x851145…3f07
4 touches
1 conflict
0xf9312173…41a7
0x851145…3f07
4 touches
1 conflict
0x066768dd…a09c
0x037848…a1f7
2 touches
0 conflicts
0x066768dd…a09d
0x037848…a1f7
2 touches
0 conflicts
0x0eaa54cf…ce21
0x037848…a1f7
2 touches
0 conflicts
0x0eaa54cf…ce22
0x037848…a1f7
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:
0x851145ea…9f3f07
1 conflict on slot
0xa59e109df5…34d53b
Audit this contract →
← previous block
·
next block →
recent activity