pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,594,417
← previous block
next block →
recent activity
Analyzing
Block #95,594,417
14 transactions · 10 stateful · 2026-08-13 09:23:13 UTC
Parallelism
86
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,594,417
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x0c7abd22
· blocks 1
#3
0x5f127e…23f7
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
#7
execFwdPositionOps
· blocks 1
#10
setData
#11
0x59558d29
#12
execOrders
#13
0x61d59c2d
#8
batchUpdate
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa77975dc…94c7
0x09475a…400f
2 touches
0 conflicts
0xc0240a50…d410
0x111111…db61
2 touches
0 conflicts
0xec3e20e7…e008
0x111111…db61
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity