pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,586,479
← previous block
next block →
recent activity
Analyzing
Block #95,586,479
11 transactions · 9 stateful · 2026-08-13 08:43:17 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,586,479
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x6df9e92b
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
verifyOracleProofV2
#6
0x94defb17
#8
resetPoolTokens
#9
setData
#10
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93dda39a…de4d
0x34b655…2a6f
4 touches
1 conflict
0xe429135d…613c
0x34b655…2a6f
4 touches
1 conflict
0xe429135d…613d
0x34b655…2a6f
4 touches
1 conflict
0x16f18cc7…466e
0x34b655…2a6f
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x714a26…182d
2 touches
0 conflicts
0x00000000…0001
0x714a26…182d
2 touches
0 conflicts
0x00000000…0003
0x714a26…182d
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
0x93dda39a8f…65de4d
Audit this contract →
← previous block
·
next block →
recent activity