pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,760,385
← previous block
next block →
recent activity
Analyzing
Block #95,760,385
11 transactions · 10 stateful · 2026-08-13 23:19:03 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,760,385
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x5acec890
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
· blocks 1
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x6a7e515f
#10
setData
#5
execFwdPositionOpsV2
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f3c2bda…9086
0x065c9d…c394
4 touches
1 conflict
0xa448dfbf…5ad6
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8d950213…cebe
0x065c9d…c394
3 touches
1 conflict
0x5fac26a6…9add
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x8f3c2bda0a…039086
Audit this contract →
← previous block
·
next block →
recent activity