pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,204,067
← previous block
next block →
recent activity
Analyzing
Block #95,204,067
10 transactions · 9 stateful · 2026-08-12 00:26:15 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,204,067
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
batchUpdate
#6
execFwdPositionOps
#7
transfer
#8
setData
#9
0x59558d29
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x19a52443…822a
0x34b655…2a6f
2 touches
0 conflicts
0x27b6292b…b88f
0x34b655…2a6f
2 touches
0 conflicts
0x3c038356…cdbc
0x34b655…2a6f
2 touches
0 conflicts
0x435da443…39d8
0x34b655…2a6f
2 touches
0 conflicts
0x5c806a17…a094
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:
Perpl
1 conflict on slot
0x31b3992285…921e66
Audit this contract →
← previous block
·
next block →
recent activity