pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,613,035
← previous block
next block →
recent activity
Analyzing
Block #96,613,035
11 transactions · 11 stateful · 2026-08-16 22:48:26 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,613,035
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
poke
#2
settlePredictions
· blocks 1
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#7
transferWithAuthorization
#8
transfer
#9
setData
#10
execute
#6
0xd62522e3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3bdfb…7537
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3bdfb…7538
0x34b655…2a6f
2 touches
0 conflicts
0x109c2330…f629
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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:
USDC (USDC)
1 conflict on slot
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity