pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,556,922
← previous block
next block →
recent activity
Analyzing
Block #95,556,922
14 transactions · 10 stateful · 2026-08-13 06:14:38 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,556,922
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
matchOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execPerpOps
#6
execPerpOps
#7
execOrders
#8
execFwdPositionOps
#9
0x3f5c179b
#10
claim
· blocks 1
#12
setData
#13
0x59558d29
#11
0xc925b3a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0626b45…e96e
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xb0626b45…e96f
0x968279…9342
3 touches
1 conflict
0x43fd3667…094b
0x34b655…2a6f
2 touches
0 conflicts
0x5b30a6e6…b249
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
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:
0x96827978…f09342
1 conflict on slot
0xb0626b4551…56e96e
Audit this contract →
← previous block
·
next block →
recent activity